deps

There's a DEP discussion going on at https://github.com/django/deps/pull/65. Though I kind of gave up on it for now, I don't believe it'll be accepted in the current state of mypy and typing ecosystem. Try 'django-stubs' mentioned above too https://github.com/typeddjango/django-stubs, it's mostly complete. Mypy plugin inside takes care of a lot of stuff. Disclaimer: I'm a creator of the 'django-stubs'

https://www.aeracode.org/2018/06/04/django-async-roadmap/ https://github.com/django/deps/blob/master/accepted/0009-asy...

The author writes that they have a particularly big piece of maintenance coming up. > The latest change we need is an especially large amount of work, as we will have to move from Python 2 to Python 3. This sounds like the transition from Django 1.11 to (probably) Django 2.2, if they're moving from LTS to LTS, and it definitely is a big piece of work if you also have to change python versions. Django defined a release schedule DEP[0] a few years back to try to preference stability and reduce the amount of maintenance when moving between LTS versions, which is approximately every 3 years. If your application runs on an LTS version without any deprecation warnings, then you should be able to move to the next LTS version without any changes. Which is nice in theory, but 3rd party packages in particular aren't always aligned in such a nice wa

DEP 0008 ('Formatting Code with Black') was accepted by the Django board last week. They're going to wait until Black has a stable release before reformatting all the code, as there's at least one thing they don't like about how Black handles things. https://github.com/django/deps/blob/master/accepted/0008-bla... https://groups.google.com/forum/#!topic/django-developers/7G...