You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The release of platformdirs 3.0.0 seems to have broken our environments the next time we tried to bump up our lockfile versions.
virtualenv 20.4.7 is almost two years old and causes issues in our environments such as:
$ python -m virtualenv venv
...
setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
KeyError: 'scripts'
Setting the dependency to platformdirs = "<3" in pyproject.toml is a temporary work around.
The text was updated successfully, but these errors were encountered:
I would guess that Poetry tries to update platformdirs and then has to trace backwards to find a virtualenv where there wasn't an upper bound on platformdirs 🤔 .
With this Poetry (tested with Poetry 1.3.2 on Python 3.10) project:
Running
poetry update
andpip list
shows that the latestvirtualenv
is installed:But adding
platformdirs
pulls virtualenv down to a very old version:The release of
platformdirs
3.0.0 seems to have broken our environments the next time we tried to bump up our lockfile versions.virtualenv 20.4.7 is almost two years old and causes issues in our environments such as:
Setting the dependency to
platformdirs = "<3"
inpyproject.toml
is a temporary work around.The text was updated successfully, but these errors were encountered: