4 ms·
Seriously, I wonder how many of the people who proclaim "no end in sight" for 2.7 are actually using Python. In the usage I can see, the majority of the ecosyst
by StavrosK 8y ago
Seriously, I wonder how many of the people who proclaim "no end in sight" for 2.7 are actually using Python. In the usage I can see, the majority of the ecosystem seems to support 3, and at least a large minority has stopped supporting 2.
- Analemma_ 8y agoI think they’re both true. People who are “extremely online” and up-to-date with technology developments are all done with Python 2.7 and can say the end is near, but they’re not the only people. There’s an entire dark matter world of businesses still on 2.7, maintained by people who don’t live in the Bay and don’t read Hacker News, and so they’re largely invisible. It will be a long time before they all switch.
- Bahamut 8y agoEven in the Bay Area there are companies still with Python 2.7 with no real migration strategy yet. I maintain several such packages at work myself.
- StavrosK 8y agoI don't know, we have a codebase of 100k loc of Python 2.7 and I migrated much of it in two or three weeks myself. I don't think the fact that companies don't spend some time drawing up a strategy is the language's problem.
- not2b 8y agoMy company is one of them: plenty of legacy Python and no plans to switch to 3.x that I am aware of.
- StavrosK 8y agoWhat about the people who do read HN and comment here? My reply was to one such comment.
- mnd999 8y agoI had to write some 2.7 the other day - a vendor supplied docker image we needed to run a script on only supported that version. Until stuff like that goes away, we’re still gonna be stuck with 2.7.
- StavrosK 8y agoIn that sense, we're still stuck with FORTRAN, but that's not indicative of the ecosystem at large.
- staticassertion 8y agoMost Python code being written today is almost certainly Python 2. Or at least it's close. Google is still Py2 I believe, as is Dropbox. These are big Python shops. I write Python. I don't see an end in sight, yet. There is, however, forward progress.
- pseudalopex 8y agoWriting code compatible with Python 2 and 3 has been possible for over 5 years. Dropbox migrated to Python 3.[1] So did Instagram. [1] https://blogs.dropbox.com/tech/2019/02/incrementally-migrating-over-one-million-lines-of-code-from-python-2-to-python-3/ https://blogs.dropbox.com/tech/2019/02/incrementally-migrati...
- staticassertion 8y agoDropbox migrated their desktop client code to Python 3.
- pseudalopex 8y agoI got the impression from someone at Dropbox that it was more than that. That's all I know, though.
- deleted 8y ago[deleted]
- joshuamorton 8y agoThey just spoke at pycon of having 3? Million LoC using mypy. While some of that is probably using the backports (comment syntax), I'd expect that much of it uses the newer syntax and therefore python3.
- deleted 8y ago[deleted]
- 8y ago
- roel_v 8y agoFor those of us in the GIS space, 2.7 will be with us for a long time, as it's the only version that is supported by ArcGIS 10.x series. To say that people aren't rushing to ArcGIS Pro (which support 3.x) is quite an understatement, I expect to be writing Python 2.7 code for 5 years at the very least.