5 ms·
Great stuff. But what about alternative python interpreters that have been lagging behind? Jython is 2.7.1 and IronPython is 2.7.9
by adamhepner 7y ago
Great stuff. But what about alternative python interpreters that have been lagging behind? Jython is 2.7.1 and IronPython is 2.7.9
- robin_reala 7y agoIronPython is a dead project at this point…
- DonHopkins 7y agoWell, he's... he's, ah... probably pining for the fjords.
- icebraining 7y agoFor the JVM, there has been some work on new interpreters for Python 3 based on GraalVM. Unfortunately none seem production-ready at the moment.
- toyg 7y agoThey are effectively both dead or moribund. Jython has had a py3 experimental branch for ages but the entire project is basically starved of money and effort. To be honest, the whole “Python on other runtimes” movement, as a concept, is more or less over. It’s just too much effort for too little reward, now that CPython has good libraries for pretty much anything you can think of.
- sjwright 7y agoDoes that view include PyPy? I'm not deep into Python (aside from the Monty kind) but it seems to be maintained and makes performance claims.
- toyg 7y agoPyPy is a python-focused project that builds a python-focused runtime. My comment was more about projects trying to retrofit Python on top of runtimes that were built for very different languages, typically because of some constraint that has now disappeared.
- mixmastamyk 7y agoThe GIL constraint has not.
- toyg 7y agoIf the GIL is so important to you that you're willing to suffer the pain of running on another VM with a much-reduced ecosystem, while at the same time having requirements so complex that PyPy cannot meet them, maybe Python is just not the right tool for the project.
- mixmastamyk 7y agoMoved the goalposts.
- toyg 7y agoI am sorry that you see statements of fact and acceptance of reality as an adversarial debate.