env: installing into MockEnv
should not have side effects on another env
#7141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.