Comment 3 for bug 1912248

Revision history for this message
Stefano Rivera (stefanor) wrote :

The issue is that virtualenv bundles pip 8.1.1, which doesn't know about python_version. It then tries to upgrade to the latest pip and setuptools, but that version isn't Python 3.5 compatible.

If you build the virtualenv with --no-download, or use venv instead of virtualenv, you'll get just pip 8.1.1, and setuptools 20.7.0. You can then explicitly upgrade them to setuptools < 51.3, as you describe.

We could add a hack to virtualenv to specify the setuptools < 51.3 restriction.
But given Ubuntu 18.04 is almost EOL, I'm tempted to just leave this one be. It has a workaround...