3 ms·
> i.e. only use the most basic and generic Django features I don't think you need to do this with Django. Features are generally very mature, stable, and are n
by danpalmer 7y ago
> i.e. only use the most basic and generic Django features
I don't think you need to do this with Django. Features are generally very mature, stable, and are not deprecated frequently. When they are, they are deprecated years in advance with long term support still provided.
In all honesty, I've seen very few projects run feature lifecycles as well as Django. I'd use everything you need to in it without concern about this.
- StavrosK 7y agoSeconded, I haven't really had many problems upgrading Django projects, and I've upgraded a lot of them.
- danpalmer 7y agoYep. I work on a codebase started with 1.4 and we're on 2.2 now, and almost all of that was straightforward. The biggest difficulty was migrating from South to Django migrations, and that was only because we did it between real releases on Django's master branch (we don't do that anymore!).