• bloopernova@programming.devEnglish
    17·
    11 months ago

    The reason has been purged, intentionally forgotten. Vulcans train their entire lives to take on a dangerous task: once every 66 years, the very best of the best view the reason why Python is banned. Once viewed, the Vulcan confirms that it is indeed a just and necessary action to ban the ancient language.

    After the task is complete, the Vulcan goes utterly, irretrievably insane and dies mere hours later.

    • cheery_coffee@lemmy.caEnglish
      9·
      11 months ago

      It’s the GIL isn’t it?

      I think Vulcans wouldn’t develop any higher order languages, as programming in assembly with some solid logic is free from leaky abstractions.

      • MajorHavoc@lemmy.worldEnglish
        3·
        11 months ago

        It’s clearly because someone had to work with the Python logging package. Or had to call subprocess.

        • cheery_coffee@lemmy.caEnglish
          3·
          11 months ago

          Subprocess is great, just UTF8 encode your strings and never ever ever pass input or receive output from the sub process.

        • bloopernova@programming.devEnglish
          2·
          11 months ago

          Logging is fine, it’s traitlets that I’m struggling with right now. Lack of comprehensive documentation means I have to read the source and that is taking me forever.

          • MajorHavoc@lemmy.worldEnglish
            2·
            11 months ago

            Interesting. Traitlets looks to Java-like (overly in love with objects) for my taste.

            For typing, I’ve been reasonably happy with MyPy.

            For everything else in Traitlets - well, that all sounds too OOP for my comfort.

            Ooh, that’s another reason to burn Python to the ground and never speak of it again - it supports multiple-inheritance.