[bjacobel]

There is no advantage to 2 unless you're using a legacy environment or a legacy dependency.

Edit: the "Python 3 Wall of Superpowers"[1] is a good resource for seeing how far the ecosystem's conversion to Py3k has come. Many of the "red" packages even have Python 3-compatible forks (e.g., Supervisor).

[1]: https://python3wos.appspot.com

[crdoconnor]

There are still a lot of libraries which haven't moved yet.

I periodically check my requirements.txt's and there's still a few big holdouts left.

[rspeer]

Which are they?

I know that python3wos is out of date regarding the libraries people actually use. When I look at the py2-only libraries on there, I see:

- the big "legacy dependencies", Twisted and gevent

- libraries that are ported but the site doesn't know it, such as protobuf

- highly specific code to extend a particular system, such as tiddlywebplugins

- system utilities that it doesn't matter what language they're in, such as supervisor and Fabric

- libraries that have been abandoned (in all versions) and superseded, such as MySQL-Python

I'm not saying you're wrong, I'm saying that we need a better python3wos. It makes it look like "unless you bet on a massive legacy asynchronous framework, you're fine".

I think that to some extent this should be the case, but to some extent, there are things that should be ported that we're not seeing because of the unrepresentative set of packages on python3wos.

[crdoconnor]

Twisted is one, and it's there partly because a lot of code relies upon it, not because I like it. I also use a few niche libraries which haven't been bumped and there's a few libraries like mechanize too - not so niche yet still not bumped.

Honestly, if there were some big incentive at this point I would go through the hassle of upgrading, but there isn't. The gains on python 3 seem relatively minor and incremental.