Allow importlib-metadata v3 #1763
Labels
feature:new
something does not exist yet, but should
Comments
pkolbus
added a commit
to pkolbus/tox
that referenced
this issue
Dec 24, 2020
Since importlib-metadata is a backport from CPython, new major versions are much more likely to be to adjust supported Python versions, and not change the API. Remove the upper bound on the version constraint. Closes tox-dev#1763.
6 tasks
gaborbernat
pushed a commit
that referenced
this issue
Jan 3, 2021
Since importlib-metadata is a backport from CPython, new major versions are much more likely to be to adjust supported Python versions, and not change the API. Remove the upper bound on the version constraint. Closes #1763.
ssbarnea
pushed a commit
to ssbarnea/tox
that referenced
this issue
Apr 19, 2021
Since importlib-metadata is a backport from CPython, new major versions are much more likely to be to adjust supported Python versions, and not change the API. Remove the upper bound on the version constraint. Closes tox-dev#1763.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
importlib-metadatapackage is at version 3 as of about a month ago;toxshould be updated to allow it. This can help with conflicts when using the old pip resolver (pip<20.3) and not cause a package downgrade iftoxis installed aftervirtualenv.virtualenvsolvedimportlib-metadatasupport by removing the high constraint in pypa/virtualenv#2019, and it looks like the rewrite branch got a similar treatment in #1556. (And since importlib-metadata is a backport from CPython, removing the upper bound seems like the right approach).The text was updated successfully, but these errors were encountered: