-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests are broken with virtualenv's rewrite (>=20.0.0) #8273
Comments
Huh, I thought I'd filed a tracking issue for this task, but seems like I hadn't. :) |
#8441 should also get a back-link. |
Adding
https://github.com/hugovk/pip/actions/runs/981825354 Python 3.10 beta 3 is out, with 3.10.0 final due on 2021-10-04: |
Looks like we just got a deadline for finishing this migration. :) |
I hope we can find enough resource for this to happen. Rewriting the test helpers is a giant time sink and I don’t think we’ll get enough contribution without outside help. |
This is now a major annoyance for me, since the legacy virtualenv does not have support for my shiny new Apple Silicon laptop. :/ |
Excellent, that means you're motivated to fix it now 🙂 More seriously, if you do look at this, ping me if you want reviews/help, I took a brief look at it a while ago but didn't have enough time. |
…and now this became even more important since virtualenv-16 doesn't work on Python 3.11 at all:
(I've confirmed with GHA in case it was my install: https://github.com/mgorny/pip/runs/6400925082) It's also broken with PyPy3.9 but AFAIR pip's tests never worked well with PyPy3. |
#11044 (comment) has some more discussion. |
Hmm, it seems that the new releases pass tests with the new virtualenv. Should this be closed now, or is there anything left to do? |
#11288 is the relevant PR. We're still using it on < 3.10. |
It’s quite unlikely we’re ever going to fix <3.10 though, since it needs us to monkey-patch either distutils or virtualenv, which is not really worthwhile IMO (these are just test setup, not actual pip code—not even code to test pip). So I’d say it’s OK to close this anyway. |
Well, maybe I'm doing something wrong but it seems that the test suite passes for me with on py3.9 with the newest virtualenv. That said, 3.9's going out of Gentoo in 3-4 months anyway, so not a big deal for me. |
I'm going to say that this is done. We have better things to focus our resources on than getting the test suite to play nicely with modern virtualenv on Python 3.8 and 3.9. |
Environment
Description
After upgrading to virtualenv-20.0.18, all pip tests fail due to missing
path_locations
. I know you know that but I couldn't find any bug tracking this.Expected behavior
I would expect pip tests to work with current releases of virtualenv, however crazy that sounds.
How to Reproduce
Change
tools/requirements/tests.txt
to list plainvirtualenv
instead of legacy branch. Runtox
.Output
The text was updated successfully, but these errors were encountered: