4 ms·
I don't think they're doing anything in particular to hinder PyPy -- the damage was done long back, when things like the C-API exposed too much detail on CPytho
by setr 6y ago
I don't think they're doing anything in particular to hinder PyPy -- the damage was done long back, when things like the C-API exposed too much detail on CPython internals that severely limit PyPy's potential to replace it with more optimal systems/datastructures
- sitkack 6y agoThe issue with crowding out alternative Pythons is a socio-political one. The C-API issue is as well, as you said Python extensions are over coupled to the runtime. ctypes and subsequently cffi fixed this 10+ years ago. 1. Decouple the extension mechanism. Use cffi 2. Modularize the batteries Each alternative Python has to re-implement large swaths of the stdlib. The code is the spec in Python. Stackless got the PyPy treatment before PyPy even existed. Besides PyPy, we now have graalpython, rustpython and ... https://github.com/beeware/ouroboros/issues/21 https://github.com/beeware/ouroboros/issues/21 points to a python stdlib I had never heard of, https://github.com/pfalcon/pycopy-lib https://github.com/pfalcon/pycopy-lib The point is, the core CPython devs need stop being so selfish with their toys. The greater Python ecosystem is diverse in spite of their actions not because of it.
- ksec 6y agoIt is similar situation in CRuby as well.