3 ms·
I plan to do exactly that. It's vaporware at the moment, but uh: https://git.sr.ht/~sforman/Bladders https://git.sr.ht/~sforman/Bladders > Maintenance-mode fo
by carapace 7y ago
I plan to do exactly that.
It's vaporware at the moment, but uh: https://git.sr.ht/~sforman/Bladders https://git.sr.ht/~sforman/Bladders
> Maintenance-mode fork of the officially-deprecated Python 2 interpreter and standard library. Bugs fixed, security holes patched, and maybe some performance improvements, but no changes to the syntax or semantics (for that see the Tauthon project, unaffiliated.)
- - -
Sometime between now and the end of the year I'm going to fork Py2 and set up build jobs to run the test suites. (Maybe later today, it's not hard, it just takes a few spare hours.)
Going forward I plan to work on things like improvements to the docs, curating additional packages and libraries (additional to the standard lib), and language tooling (I'd like to keep things like Nuitka, Snakefood, etc. working.) I also want to run fuzzers and other code quality tools over it all.
- sundarurfriend 7y agoBefore it's too late, I'd like to humbly suggest a name change. Even as a Blackadder fan, the name sounds terrible at a glance, especially for such a (potentially) high profile project. Naming isn't everything, of course, but it has more significance than we consciously realize. It can subconsciously impact decisions in favour of or against the project, as irrational as that is.
- carapace 7y agoI appreciate the sentiment but it's deliberate. I don't want to become high profile. The Python folks have made it pretty clear that they don't want continuity of Python 2 to "dilute the brand" of Python-as-Python-3, so I wanted to wave a big "Don't take this too seriously!" flag over this fork. (Also for the BBC, eh? It would be a little on the nose to call it "Blackadder". Or "Baldrick".)