Removing Python 2.x support from Django for version 2.0

Re:Removing Python 2.x support from Django for version 2.0 by LeifCarrotson on Thursday January 19, 2017 @08:24AM (#13435548)

> there are actual numbers for Pypi supporting that. What do you have to counter these?

99% of Pypi traffic is composed of mirrors and bots. Python 3 toolchains are more likely to use tools like devpi, wheel, and Docker to cache their packages, while Python 2 toolchains are often going to hit Pypi directly.

We're concerned about which version has the majority of users, not about which has more downloads on Pypi.

[ Parent | on HN ]

Re:Removing Python 2.x support from Django for version 2.0 by lima on Thursday January 19, 2017 @10:11AM (#13436335)

Exactly. PyPi numbers are totally meaningless. It's commonly used for installing applications (that's how packages like supervisor end up in the top 20) and used in all sorts of CI scenarios.

Every OpenStack build, for example, pulls in hundreds of packages from PyPi.

In terms of real-world use, all of the Python devs I personally know moved to Python 3.

[ Parent | on HN ]