Skip to content

chore: un-pin virtualenv update - #1830

Merged
henryiii merged 1 commit into
pypa:mainfrom
mayeut:virtualenv-update
May 20, 2024
Merged

henryiii merged 1 commit into
pypa:mainfrom
mayeut:virtualenv-update

Conversation

@mayeut

@mayeut mayeut commented May 18, 2024

Copy link
Copy Markdown
Member

virtualenv has been pinned to 20.21.1 in order to be able to create python 3.6 venvs.

This commit allows to pin virtualenv for given versions of pythons which in turns re-allows updates as a default.

@mayeut
mayeut marked this pull request as draft May 18, 2024 16:32
@mayeut

mayeut commented May 18, 2024

Copy link
Copy Markdown
Member Author

converting to draft while I debug Windows builds.

virtualenv has been pinned to 20.21.1 in order to be
able to create python 3.6 venvs.

This commit allows to pin virtualenv for given versions
of pythons which in turns re-allows updates as a default.
@mayeut
mayeut force-pushed the virtualenv-update branch from f1d44ee to c177ca5 Compare May 18, 2024 18:23
"""
pip=={pip}
delocate=={delocate}
importlib-metadata<3,>=0.12; python_version < "3.8"

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Failing tests on windows came from this pin.
I'm not sure exactly why since I can't really debug on Windows.
All I can say is that it was causing some backtracking in the pip resolver in order to install an old version of virtualenv (2.16.2).

@mayeut
mayeut marked this pull request as ready for review May 19, 2024 06:14
@henryiii
henryiii merged commit d1a4c9c into pypa:main May 20, 2024
@mayeut
mayeut deleted the virtualenv-update branch May 20, 2024 06:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants