3 ms·
That's top-down change from the PSF/core dev team and some major library developers added dual 2/3 support. The users never arrived and it'll be 10 years Python
by BuckRogers 10y ago
That's top-down change from the PSF/core dev team and some major library developers added dual 2/3 support. The users never arrived and it'll be 10 years Python3 has been available next December. I'd like to unify Python again but we as users didn't break it either. 10 years any reasonable person in charge would hang it up or change course.
Grumpy is pretty much what most everyone would actually want out of a new Python and may have arrived just in time.
- lima 10y ago> some major library developers added dual 2/3 support > The users never arrived That's the way it used to be a few years ago - it changed a lot the last few years. Pretty much all libraries are ported and many new libraries are Python 3-only. asyncio is nice. All Python devs I personally know moved to Python 3. Porting is a lot less painful than it used to be.
- BuckRogers 10y agoGevent is nice. AsyncIO is terrible[0]. [0]http://lucumr.pocoo.org/2016/10/30/i-dont-understand-asyncio/ http://lucumr.pocoo.org/2016/10/30/i-dont-understand-asyncio...
- orf 10y agoIt's actually ridiculously nice, especially with the new async/await constructs.
- dismantlethesun 10y agoPython 3 is largely cross-compatible with Python 2. If you're not working with unicode, not reliant on perfect floating point division, and not using aysncio, then chances are what you produce will work just fine on Python 2.