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

env: installing into MockEnv should not have side effects on another env #7141

Merged

Conversation

radoering
Copy link
Member

As noticed in #6205 (comment), when using the new installer, tests will pollute poetry's own virtualenv. We've even had a problem like that without the new installer in one test case in editable_builder.py. This issue has been fixed for this specific test case in #6929. Especially with regard to #6205, I think we should take a more general approach: Installing into a MockEnv should not have any side effects on other environments. I don't think it makes sense to imitate a specific installation scheme, so I just use distinct, clearly named paths.

@radoering radoering merged commit f594246 into python-poetry:master Dec 5, 2022
@neersighted neersighted added the area/testing Related to the test suite label Dec 21, 2022
@neersighted neersighted added this to the 1.3 milestone Dec 21, 2022
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 29, 2024
@radoering radoering deleted the mockenv-without-side-effects branch November 24, 2024 12:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/testing Related to the test suite
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants