Meanwhile, the Python 3 Wall of Superpowers is looking really good. 166/200 major watched projects are Python 3-compatible. https://python3wos.appspot.com
Python 2.x vs. 3.x use survey
21–30 of 72 posts
Re: Python 2.x vs. 3.x use survey
#22[deleted]
Re: Python 2.x vs. 3.x use survey
#23Stopped using python in my research. Now I stick with Matlab/Julia.
Why did you stop? Surely, the 2.x vs 3.x schism didn't cause this?
Re: Python 2.x vs. 3.x use survey
#24Meanwhile, the Python 3 Wall of Superpowers is looking really good. 166/200 major watched projects are Python 3-compatible. https://python3wos.appspot.com
Python 2 was supposed to be dead at least 2 years ago and still 34/200 major watched projects use it.
Re: Python 2.x vs. 3.x use survey
#25Stopped using python in my research. Now I stick with Matlab/Julia.
Why? I ask because I switched from using Matlab to using python. I found Matlab was great for getting things done, but it was difficult to maintain/distribute larger projects--much less deal with interfaces to the web, etc. I also found (at the time) that parallelization was easier with python. I haven't experimented with Julia.
Re: Python 2.x vs. 3.x use survey
#26Meanwhile, the Python 3 Wall of Superpowers is looking really good. 166/200 major watched projects are Python 3-compatible. https://python3wos.appspot.com
pylibmc was ported to Python 3.x in its latest release, but the wall of superpowers hasn't updated in days!
Re: Python 2.x vs. 3.x use survey
#27Meanwhile, the Python 3 Wall of Superpowers is looking really good. 166/200 major watched projects are Python 3-compatible. https://python3wos.appspot.com
Python 2 was supposed to be dead at least 2 years ago and still 34/200 major watched projects use it.
Well, dead may be a bit strong. Old projects that use 2.x have no good reason to migrate to 3.x, and 2.7 will be supported until 2020 at least.
Re: Python 2.x vs. 3.x use survey
#28Still on 2.x, simply because it's a lot easier to use the generally available system packages than constantly rolling/building your own. 2.x is not missing anything I need, so there's simply little incentive to migrate my code to 3.x until the package support is there.
Re: Python 2.x vs. 3.x use survey
#29Last year a survey was conducted on python 2 and 3 usage. It sparkled interesting discussions on HN: https://news.ycombinator.com/item?id=6990481 "Python 2.x vs 3.x use survey" https://news.ycombinator.com/item?id=7005711 " Python 2.x vs. 3.x survey results" Here is the 2014 edition, slightly updated (from 9 to 11 questions). It should not take you more than 1 minute to fill. I would be pleased if you took that time.…
Where will the results be published?
I suppose on the python.org frontpage as last year.
Re: Python 2.x vs. 3.x use survey
#30This reminds me of a Flask mini project I did. I was doing it in Ubuntu (LTS if I'm not mistaken). I picked python3 and ran with it. As I tried to use Python's virtualenv (venv), I went down the rabbit hole of a broken mess that was left in Ubuntu. I just reinstalled Ubuntu this week so I might give it another shot, but every time I try to do something with Python I end up with a broken mess, and that's disheartening
I'm not doubting your specific experiences, but I set up a Flask project with Python 3 on an Ubuntu system myself about three months ago, and - as someone with a lot of experience with Linux and Ruby (and other things) but relatively little with Python - I didn't have much trouble. It definitely could have been easier, and I think I did have to google a few incantations to make it all work, but it didn't seem terribly hacky or messy to me, and probably no worse than getting the equivalent Ruby/rvm/Sinatra project to work.
(Other comments suggest that there are fundamental problems with Python and virtualenv and Ubuntu, so either I just fortuitously missed all of that or maybe I was in such a happy delirium of tinkering that I've now forgotten all about it.)