-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop Python 2 support. #6277
Drop Python 2 support. #6277
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @auvipy. I think we're good to go given the ticket: we'll drop Py2 for 3.10.
Are you happy to make a good first pass at the code changes with this? (Or we can pull these changes into a bigger PR...?)
Thanks for making the start. It's 💃🏼
But we don’t run stable branches. We can’t merge this until we’re sure there won’t be more 3.9.x releases. |
Can you pull them into one branch/PR please. (Separate commits for each stage are fine.) |
OK I will put all changes in this branch |
…decorator from utils
seems like I accidentally removed some working code in generic relations tests |
how to fix this? |
what is the alternative of from django.utils.six.moves import reload_module? |
well, should we move the six import clean up to another PR? or the six compats should be kept for few more versions? |
Fixes #6230