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.
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.
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.
deleted by creator
It’s clearly because someone had to work with the Python logging package. Or had to call subprocess.
deleted by creator
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.
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.
I’m going with Vulcans using APL*. Why create a language that makes you do more than just write the equations?