Here's some light benchmarking (this was posted a few weeks ago I think...) https://hackernoon.com/which-is-the-fastest-version-of-pytho...

Basically once 3.7 is out (which is soon), CPython3 will finally be broadly faster than CPython2.7.

Interpreter startup time is still annoying though. I really wonder what the right strategy for addressing that is. Like honestly 2.7 is faster than 3.x, but 2.7 CLI tools still feel silly to use.

If you are doing raw number crunching you shouldn't be using python in the first place, the whole idea of python is that it makes it easier to write better algorithms lowering your big-O, or use python for the lightweight orchestration and call into native processing libs or external processes such as numpy for the heavy lifting. Same goes for distributed computing which is becoming much more popular; asyncio, await, and other improvements from py3 makes it easier to write fast and robust distributed code, improving your overall application performance.

So it took only a decade to bring Python 3 to levels of Python 2? Victory!

Perfect example of how not to use plots. Y-axis simply says mean, mean of what? I can't tell if lower is better or worse.

> light benchmarking

Thanks for this!

Do you know of any more longer term, less light Py2/3 benchmarking?

> "Most popular" packages, which ones? Most moved a long time ago to Python 3

http://py3readiness.org/

Thanks for proving my point

There's Fabric3, MySQL libs that work with Python3 (and Django), futures are a backport of a feature from Python3, uWSGI and BeautifulSoup might be worrying but the site shows mostly green

At this point if the library hasn't been ported to Py3, someone else would have done it for you or abandoned it.

Edit: Thanks for the updates!

BeautifulSoup4 is Python3 compatible. It was released under a new name.

uWSGI has Python3 support as a module.

I have been using both on Python3 for many years. I don't think there is any python module left which does not have Python3 support or a more modern, better alternative.

And BeautifulSoup is the not-supported older version, not BeautifulSoup4 which runs on Python3 just fine.

I think ansible is a big one for RHEL though.

Ansible works just fine on python3 for both local and remote actions. You need to explicitly tell it to use python3 at the moment, but this will go away eventually.

There are a couple modules with options that break in a Python 3 environment, but that number is I think in the single digits now. I’m very close to switching all my Ansible masters to 3 finally.

> "Most popular" packages, which ones? Most moved a long time ago to Python 3

The person you replied to said

> most popular packages are now compatible with Python 3

so it looks like you two are in agreement there.