After Rick's failed verification comment I had been wondering if we'd
run into trouble with stale seed-app-data, and yes we have 2 different
regressions:

1. The new python-pip-whl breaks new virtualenv creation if you have existing 
seed-app-data.
   This was James's issue. Traceback ends with:
   File "lib/python3.8/site-packages/pip/_internal/pyproject.py", line 8, in 
<module>
     from pip._vendor import pytoml, six
   ImportError: cannot import name 'pytoml' from 'pip._vendor' 
(lib/python3.8/site-packages/pip/_vendor/__init__.py)

2. The new virtualenv breaks new virtualenv creation if you have existing 
seed-app-data.
   File "lib/python3.8/site-packages/pip/_internal/exceptions.py", line 10, in 
<module>
     from pip._vendor.six import iteritems
   ModuleNotFoundError: No module named 'pip._vendor.six'

Attached is my script to reproduce.

This is all pretty horrible. I'm tempted to patch out seed-app-data entirely 
for our use-case. But
I see the whole seed-app-data mechanism was re-done in 20.0.24, hopefully it 
will be more friendly to patching...

My solution is:

1. Bump the seed-app-data version in python3-virtualenv, to cache-bust.
2. Add a Breaks: python3-virtualenv (<< 20.0.17-1ubuntu0.3) (the version in 1) 
to the new python-pip-whl.

** Attachment added: "Reproducer script"
   
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1880749/+attachment/5467765/+files/upgrade.sh

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880749

Title:
  Ubuntu 20.04: virtualenv: pep517 requires toml, but it isn't bundled
  in venvs

To manage notifications about this bug go to:
https://bugs.launchpad.net/pip/+bug/1880749/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to