4 ms·
As a Python2 holdout, I'm glad they extended the EOL -- and I'm actually glad I held out this long, starting some python3 stuff now and things work -- libs and
by mattbillenstein 9y ago
As a Python2 holdout, I'm glad they extended the EOL -- and I'm actually glad I held out this long, starting some python3 stuff now and things work -- libs and tools that I'm used to in python2 seem all there in python3.
- dfee 9y agoIf you don’t continue to hold out, who will? And, if you move on, are we losing access to living history?
- mattbillenstein 9y agoWhat do you mean? Python2 history I see as preserved in the cpython repo, mailing lists, etc. Python3 has enough improvements in the CPython VM to warrant upgrading at this point.
- oliwarner 9y agoLet's maintain every version of everything ever made, forever. Won't somebody please think of the children! But if that wasn't sarcasm, nobody's removing "access" to this historical artefact. Python 2's source code is available as long as somebody stores it. But the resources required to keep it secure are needed elsewhere. If you simply want to preserve it, talk to an archivist. The Python community has moved on.
- dfee 9y agoIt was sarcasm!
- mattbillenstein 9y agoPlease use <sarcasm>Something sarcastic</sarcasm> as appropriate ;)
- malcolmgreaves 9y agoWhy are you a Python 2 holdout? What are you holding out for?
- mattbillenstein 9y agoEarly adopters are beta testers ;) I think until about 2014 (3.4) Python 3 just wasn't really ready. Then maybe it took another two years for library and tooling support to firm up around that. In 2016 I did start a new project, but a mix of familiarity and gevent support kept me on 2.7. Also, until recently the runtime had no real advantage over 2.7, but there have been some incremental improvements (dict shared keys and so forth) that are a win you get in Python 3 for free basically. Working on a new project in 3.6 now and it's looking good so far.