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 support for Python 2.x and Django < 2.2 #2201
Comments
We want to give users early warning on dropping Python 2 support, this way hopefully nobody will be suprised when 4.0 is out next year. Issue #2201 Signed-off-by: Michal Čihař <michal@cihar.com>
This has been scheduled to April 2020 in the 4.0 milestone. It will also not support older Django than 2.2, which will be current LTS release by then. |
We can get rid of those once we drop support for Django 1.11. See #2201 Signed-off-by: Michal Čihař <michal@cihar.com>
We might actually go for whatever Django will include django/django#12332 so that we can remove our workaround for that. That will make us skip LTS 2.2, but I don't see a major issue with that. |
Since Python 3.3 all builds are wide, so avoid dealing with that for now. See actions/setup-python#23 See #2201
Those were needed for Python 2.7. Issue #2201
Support for Python 2 is dropped. Issue #2201
It is more effective than iterating and yielding every item. Issue #2201
We no longer need six for that. Issue #2201
We no longer need six for that. Issue #2201
Remove usage of six as Python 2 compat is gone. Issue #2201
We can now use Python 3 names directly. Issue #2201
Own logic is no longer needed as we require Python 3.5. Issue #2201
We can use native Django features for this. Issue #2201
The 0.7.2 has native code for damerau_levenshtein_distance with unicode. Issue #2201
Now all of them are unicode. Issue #2201
It is not needed with Python 3. Issue #2201
With Python 3 the default inheritance does not have to be specified. Issue #2201
It was only needed for migrating to Python 3. Issue #2201
Thank you for your report, the issue you have reported has just been fixed.
|
This has to be done at some point. Eventually it might become problematic to keep the code compatible with Django 1.11 and current release or simply we want to get rid of all the compatibility code for Python 2.
super()
object
bulk_create_ignore
)python_2_unicode_compatible
decoratorsyield from
for nesting generatorsThe furthest date for dropping support Django 1.11 is upstream support and it is supported until at least April 2020.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: