Update constraint for importlib-metadata#1682
Merged
gaborbernat merged 1 commit intoSep 29, 2020
Merged
Conversation
gaborbernat
requested changes
Sep 29, 2020
gaborbernat
approved these changes
Sep 29, 2020
Author
|
Hi @gaborbernat, thanks for merging the fix. Could you tell me when the next release is planned for tox? Should I make a PR for releasing a new version as well to get this fix updated on PyPI, if the main release is late in the future? |
This was referenced Oct 12, 2020
ssbarnea
pushed a commit
to ssbarnea/tox
that referenced
this pull request
Apr 19, 2021
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thanks for contributing a pull request!
On Python<3.8,
importlib-metadata==2.0.0causes dependency conflicts because of the pinned constraintpython<3.8. There is no breaking change in the importlib-metadata version 2.0.0.Contribution checklist:
(also see CONTRIBUTING.rst for details)
in message body
<issue number>.<type>.rstfor example (588.bugfix.rst)<type>is must be one ofbugfix,feature,deprecation,breaking,doc,misc<your username>"superuser."CONTRIBUTORS(preserving alphabetical order)