10 ms·
Python 2 advocates were quite firm in telling us that Python 3 and its incompatibility with Python 2 had killed Python and people would abandon Python altogethe
by andrewstuart 9y ago
Python 2 advocates were quite firm in telling us that Python 3 and its incompatibility with Python 2 had killed Python and people would abandon Python altogether in droves for other languages.
This post is suggesting the opposite, that Python is more healthy than ever and growing incredibly fast.
- arikrak 9y agoMaybe the confusion over python 2 vs. 3 is why people have so many questions about it.. </snark, mostly>
- blub 9y agoThose people were advocating for stability, not necessarily for P2. The 2->3 was a pretty big screw up, and it definitely had an impact on the language and ecosystem. Python seems to have overcome that (keyword: seems), thanks to a strong offering in data science, but 2->3 is still a headache. I never really used Python for application development, but rather for utility/scripts and I am still on 2, because I don't need more. 2 is available out of the box on all OSes and at work we also use 2 for building tools. I have the feeling that Python is still losing people to Golang due to its weak performance and Golang's reputation in that area. So instead of being arrogant about 2->3, I'd say Python devs should be thankful to data science for saving their butts. :)
- fleurdelotus 9y ago>>Python is still losing people to Golang Any source (other than Rob Pike) ?
- blub 9y agoAnecdata I'm afraid, hence "feeling". This can only be solved through an actual market study. The SO post is not the study we need, because it uses a proxy variable (SO tags).
- goatlover 9y agoI doubt Python is losing people to Golang in scientific computing.
- jacquesm 9y agoThat's not the way to look at this. The control you would need to establish whether what you are saying is true is a world in which the 2/3 split never happened. And in that world Python is most likely doing even better than in this one... They fucked up. That Python is resilient enough to absorb such a blow and that no other language is a viable alternative for that particular niche is what saved the day. And even now there is still plenty to improve on, fortunately Anaconda at least makes package management more sane.
- imtringued 9y agoI feel like it's still a better idea to migrate back to python 2.7 and update it to match python 3 features in a backwards compatible way. At the very least there needs to be a way to interop between python 2 and python 3 code without modifying the python 2 code. I haven't used python for a while though. Maybe they found a solution to the python 2/3 problem already.
- pen2l 9y agoThree of us (including me), in an academic lab, are making the jump from matlab to python. We use py3 (of Anaconda, on Windows10). We like it, but we are constantly screaming and bitching about the complications of 2<->3 ("Ahhh X and Y module only works on py2!", "Ahhh device developer only provides example code for Labview and Matlab!", "Ahhh python isn't even supported for this device/application!"). Package management ("Do I use conda? pip? easy_install? compile?") is annoying, I hope that something like hatch (https://github.com/ofek/hatch https://github.com/ofek/hatch) maybe takes over everything -- because I think the mess that is package management is THE biggest deterrent for newcomers. I think the one thing we are all learning from this experience is: JUST USE UBUNTU, doing python with Windows is a headache. All of that said -- python is nice, it's amazing, it's the newer, funner Java. It is incredibly approachable, it can do pretty much EVERYTHING because of the expansive availability of libraries, it's finally a programming language that is great to get my 7 year old niece started on.
- BeetleB 9y ago>I think the one thing we are all learning from this experience is: JUST USE UBUNTU, doing python with Windows is a headache. Meh. I use python on Windows all the time - it's not a problem. Mostly pip just works. Of course, I have over a decade of experience with Python - albeit only the last few years in Windows.
- princeb 9y agothe #1 issue i have with py on win is having to download a million different C++ compilers esp for packages not distributed on pip, and esp the more obscure ones with no support whatsoever (e.g. data processing or math packages that were put together by some chap who was working on it for a specific set of research papers and has since moved on). chris gohlke's website was a real lifesaver back then, although now pip seems much better. nowadays it can be a bit difficult replicating environments across different machines especially since conda is moving rapidly from python ver to ver while some obscure packages i rely on are still stuck on 3.4 or earlier... or if c++ 10.0 or 9.0 or 14.0 is not set up correctly. then it becomes an issue of crossing fingers and hoping "python setup.py install" doesn't fail.
- melling 9y agoAre most developers finally making the transition from Python 2 to 3?
- StavrosK 9y agoI really don't know where this is coming from. The only people I hear talking about a 2v3 divide are my Javascript developer friends, who are saying that as outside observers. As a Python dev, I (and all the other Python devs I know) were just waiting for (and helping) libraries to start working with 3 before we can switch over. These days, all my new projects are in 3, 2 is pretty much for legacy code only.
- icey 9y agoSame experience here -- got back into dev earlier this year and decided to go with Python 3 everywhere. The only libraries I've needed that were Python 2 only were ones that weren't being maintained anyways. It's been a pretty good recency filter for me. I know that wasn't the case when Python 3 was younger, but the ecosystem is pretty dang good today.
- kevin_thibedeau 9y agoJan 1 2018 is the day I abandon Python 2 for all greenfield projects.
- baq 9y agoWe did that in 2014 in production already :)
- epalmer 9y agoI abandoned Python 2 around April 2017 for greenfield.
- oliwarner 9y agoWhy are you deliberately making things harder for yourself? You're going to need to upgrade these projects within three years. Just seems like a wasted opportunity not to get off on a strong footing.
- kevin_thibedeau 9y agoMy Python 2 code already converts cleanly to Py3 with 2to3. There will be zero effort for me to port anything when 2.7 is EOLed. I just want to be able to use the new features without dancing around the forward compatibility game.