remove stale dependency on deprecated six#613
Closed
a-detiste wants to merge 1 commit intopytest-dev:masterfrom
Closed
remove stale dependency on deprecated six#613a-detiste wants to merge 1 commit intopytest-dev:masterfrom
a-detiste wants to merge 1 commit intopytest-dev:masterfrom
Conversation
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
1 participant
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.
Hi,
I'm coming here from deschler/django-modeltranslation#705 .
I think that projects should declare a dependecy on six only if they use it, but not just in case some other project may need it, otherwise it will stay forever.
Most projects still using six today are abandonware anyway.
Greetings :-)
https://wiki.debian.org/Python3-six-removal