Python 3 in 2016
hynek.me
Python 3 in 2016
1–10 of 194 posts
Re: Python 3 in 2016
#2The PyPi download statistics are constantly being quoted as though the are some exact representation of the state of Python 3 takeup.
I'm calling this as bullshit.
How much of these downloads are computers auto updating their configurations?
How, exactly, do these stats reflect the number of people developing current projects with Python 3?
The number of legacy projects written in Python 2 will be vastly higher than the number of Python3 projects currently in development. Maybe that's what is being updated.
When a statistician does an analysis of what these numbers really mean I will believe them but until then the numbers mean precisely nothing. Or more accurately, they seem to mean exactly what the Python 2 diehards want them to believe.
My assertion is that Python 3 is very actively and healthy and the PyPi stats are just lies, damn lies and statistics.
Re: Python 3 in 2016
#3can we please stop writing articles in twitter?
Re: Python 3 in 2016
#4I think this is a nice healthy view to have about Python 2 to 3. Can't wait until python 4!
Re: Python 3 in 2016
#5I code in both 2 & 3, and had been nervous about that. New stuff with low dependencies in 3, and older stuff with Python C API dependencies in 2 (eg spreadserve.com). I was worried that the move to 3 would force migration of my 2 based code, so I'm reassured rather than alarmed by this article. The cognitive load switching between two Python dialects isn't as bad as, for instance, switching between C++ with and without STL & Boost.
Re: Python 3 in 2016
#6The PyPi download statistics are constantly being quoted as though the are some exact representation of the state of Python 3 takeup. I'm calling this as bullshit. How much of these downloads are computers auto updating their configurations? How, exactly, do these stats reflect the number of people developing current projects with Python 3? The number of legacy projects written in Python 2 will be vastly higher than…
I get my python 2 and 3 dependencies from distribution packages (Arch, Debian), and so do all people using my software. PyPi impact: Zero.
Re: Python 3 in 2016
#7I tried switching to 3 a few years ago and was burned by some libraries that didn't work or worked with bugs.
Last year though I tried again and there were absolutely no problems. It's more natural, all non-dead libraries seem to support it, and in any case I was already using "from future import" for a while.
That said, I don't really intend to port old stuff from 2.7 if I can avoid it, so I expect that 2 and 3 will coexist for a while even within the same firm
Re: Python 3 in 2016
#8The PyPi download statistics are constantly being quoted as though the are some exact representation of the state of Python 3 takeup. I'm calling this as bullshit. How much of these downloads are computers auto updating their configurations? How, exactly, do these stats reflect the number of people developing current projects with Python 3? The number of legacy projects written in Python 2 will be vastly higher than…
Hmm I’m not sure how to take this comment. The main point of the article is basically that those numbers don’t tell the whole story (even explicitly in footnote 1).
Re: Python 3 in 2016
#9I tried switching to 3 a few years ago and was burned by some libraries that didn't work or worked with bugs. Last year though I tried again and there were absolutely no problems. It's more natural, all non-dead libraries seem to support it, and in any case I was already using "from future import" for a while. That said, I don't really intend to port old stuff from 2.7 if I can avoid it, so I expect that 2 and 3 will…
That’s exactly the place I found myself in and that made me sum it up.
Re: Python 3 in 2016
#10Been thinking about learning to code, and a lot of people have recommended Python as a good language to begin with. Taking a look at this, should I be looking elsewhere?