Skip to content
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

Switch to using virtualenv's rewrite branch #7698

Closed

Conversation

pradyunsg
Copy link
Member

Let's see how our CI / tests setup reacts to newer virtualenv.

I'm pretty sure our isolation logic will be completely broken now.

@pradyunsg pradyunsg added the type: maintenance Related to Development and Maintenance Processes label Feb 5, 2020
@pradyunsg
Copy link
Member Author

Ah shucks. I forgot that @gaborbernat is on the setuptools_scm band-wagon.

@pradyunsg pradyunsg force-pushed the virtualenv-rewrite-compatibility branch from 7e01b08 to 0050e18 Compare February 5, 2020 10:11
@RonnyPfannschmidt
Copy link
Contributor

i believe using yesterdays 20.0.0.b2 should do fine

@pradyunsg
Copy link
Member Author

i believe using yesterdays 20.0.0.b2 should do fine

Well, I'm pretty sure it won't because our test suite does horrible things.

@BrownTruck
Copy link
Contributor

Hello!

I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the master branch into this pull request or rebase this pull request against master then it will be eligible for code review and hopefully merging!

@BrownTruck BrownTruck added the needs rebase or merge PR has conflicts with current master label Feb 11, 2020
@pradyunsg
Copy link
Member Author

Good bot.

@frenzymadness
Copy link
Contributor

Virtualenv 20.0.20 is available and it would be very nice if pip can use it for tests. We are going to update virtualenv in Fedora soon and the update will break tests of pip.

@pfmoore
Copy link
Member

pfmoore commented May 15, 2020

I believe the issue is that our test harness uses virtualenv APIs that were removed in the rewrite, so we need to change to remove our reliance on them. PRs are of course welcome to address this :-)

@pradyunsg
Copy link
Member Author

#7718 is a more up-to-date PR for this. I won't be able to pick this back up anytime soon. If this is a blocker for others, I welcome PRs to fix this incompatibility! I know there's a whole bunch of nuance here and a couple of assumptions in pip's test suite that get broken, but they all seem fixable to me. :)

@gaborbernat
Copy link

@pradyunsg where did this land? Is this done then?

@uranusjr
Copy link
Member

uranusjr commented Nov 3, 2020

This did not land, and AFAIK all efforts (including mine) have stalled. For me, this requires too much effort I don’t have in to re-implement the whole thing containing ten years worth of logic :(

@pradyunsg
Copy link
Member Author

Yep to what @uranusjr said.

This needs someone with enough understanding of both pip and virtualenv, to spend a decent amount of time to figure out "what used to be" -> "what should be now", and whether there's stuff in the test suite that can be directly dropped.

There's a reason I had asked around for help with this back when the rewrite was happening. I'm not familiar with the edge cases of virtualenv, and it's internals. 🙃

@gaborbernat
Copy link

I am happy to answer questions about virtualenv but unlikely at the moment that I'll start working on pip.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs rebase or merge PR has conflicts with current master type: maintenance Related to Development and Maintenance Processes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants