3 ms·
We're talking about Python 2.2 here which is literally twenty years old. You can't leverage what exists in the Python ecosystem using a version that old. Many l
by jart 6y ago
We're talking about Python 2.2 here which is literally twenty years old. You can't leverage what exists in the Python ecosystem using a version that old. Many libraries don't even permit using 2.7 anymore. I remember Python 2.2. It had so many things missing compared to what we grew accustomed to with Python 2.7's long lifetime. Going that far back with Python is a hair's width away from starting from first principles.
- mangecoeur 6y agoIt's Pyston 2.2, not Python 2.2
- deleted 6y ago[deleted]
- viraptor 6y agoIt's Pyston 2.2 not Python 2.2. this Pyston version is based on python 3.8.8. See https://github.com/pyston/pyston/blob/f71f76ff3874970d71ed4cf5de399b3e30579182/Include/patchlevel.h#L20 https://github.com/pyston/pyston/blob/f71f76ff3874970d71ed4c...
- jart 6y agoOh wow I stand corrected. I saw Py..on 2.2 in and my head for some reason I thought it was a mad science experiment to gain a performance edge by resurrecting an old version without the bloat, because Python 2.2 is something I remember very well. If Pyston is really fully committed to going their own way with a fork, I'd recommend they just go for the gold and bump up the version to 4.x, since that sends a pretty clear message to the Python project about how valuable they feel the enhancements they've made are, while avoiding confusion. Python performance is truly something we all want to see improve so maybe things will change.