Triaged
---
https://code.djangoproject.com/ticket/27730 - Document that template tags
with "as" variable assignment don't propogate variables across blocks
(accepted)
https://code.djangoproject.com/ticket/27742 - Unexpected migration on
Parent -> child model inheritence (accepted)
http
Considering the things mentioned so far are zero maintenance effort for
Django (the only downside I see is 30kB for the bundled six), I'd rather
keep the shims until 2025 rather than spend any time on a more complex
solution. These removals are all very straight forward find/replaces, so I
don'
On Saturday 21 January 2017 22:55:51 Tim Graham wrote:
>
> I'm advocating to remove the undocumented things in Django 3.0 (released
> Dec. 2019) or later without a deprecation. By that time, I hope third-party
> apps won't support Python 2 either and so part of adding Django 3.0
> compatibility wi
As we worked on removing Python 2 compatibility code from master this week
[0], we collected a number of import shims and functions that are only
needed for code that wants to support Python 2 [1].
So far there is django.utils.six, as well as some undocumented things:
- django.utils.lru_cach
