This bug was fixed in the package python-virtualenv - 15.0.1+ds-
3ubuntu1.1
---
python-virtualenv (15.0.1+ds-3ubuntu1.1) xenial; urgency=medium
* Pin pip and setuptools to versions compatible with Python 2.7 and 3.5.
(LP: #1912248)
-- Stefano Rivera Wed, 27 Jan 2021 11:29:14
I also verified the fix with a python2 virtualenv.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912248
Title:
virtualenv on xenial: easy_install syntax error
To manage notifications about this bu
I have verified fix in amd64 xenial VM.
Test case:
* `sudo apt install python3-virtualenv virtualenv python-virtualenv`
* Confirm that any `pip` operations fail as per bug description
* `virtualenv -p /usr/bin/python3 venv/py3 --verbose`
* `source ./venv/py3/bin/activate`
* `pip list`
* Ena
Hello Peter, or anyone else affected,
Accepted python-virtualenv into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/python-
virtualenv/15.0.1+ds-3ubuntu1.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this n
** Description changed:
+ [Impact]
+
+ * Since Xenial has released, setuptools and pip have dropped support for
+Python 3.5 (and 2.7), upstream.
+ * Virtualenv installs the latest upstream pip and setuptools during
+virtualenv creation, from the Internet.
+ * Python packages gained a
@stefanor
Thanks for the explanation.
I have a one liner workaround now:
```
virtualenv -p /usr/bin/python3 venv/py3 --verbose --no-download && .
venv/py3/bin/activate && python3 -m pip install --upgrade 'setuptools;
python_version >= "3.6"' 'setuptools<51.3.0; python_version < "3.6" and
pyth
** Changed in: python-virtualenv (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: python-virtualenv (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
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
I have found the following workaround on Ubuntu 16.04 Xenial
Do not install setuptools on virtualenv creation:
`virtualenv -p /usr/bin/python3 venv/py3 --verbose --no-setuptools`
Install a supported setuptools version after virtualenv creation and
activation:
`python3 -m pip install --upgrade '
This is being tracked in setuptools upstream too
https://github.com/pypa/setuptools/issues/2541
The cause is that python-virtualenv is pulling in setuptools 51.3.3
`virtualenv -p /usr/bin/python3 venv/py3 --verbose`
```
snip...
Installing setuptools, pkg_resources, pip, wheel...
Collecti
10 matches
Mail list logo
