[djaychela]

I'm only a beginner with Django, but I tend to agree to a point - reason being is that I've found old code that I want to use (github, etc.), but it targets Django 1.x (later versions, say 1.10), and will use a load of stuff which is now removed. The issue I've had is that the documentation seems to be difficult to find these removed elements - such as last week, looking for the {% ssi (file) %} tag, which it took me the best part of an hour searching to find out which version it came from - and indeed that it was a standard tag!

A lot of the imports seem to move around (which is easy to fix, once you know where they now are), and some things have just vanished.

I know documentation is a nightmare to produce, but there must be a way to automatically produce it for either import relocations or deprecations so you can find things like this easily?

[Daishiman]

Sorry, but Django is the best framework I've found for managing deprecations.

In the web world it's quite frequent to have major versions every couple years that break everything and require substantial dev cycles to keep up.

That said, 1.x applications are quite old by now.