#18975: Remove explicit support for bad practices
-------------------------------------+-------------------------------------
Reporter: FunkyBob | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.4
Component: Database layer | Resolution:
(models, ORM) | Triage Stage:
Severity: Normal | Unreviewed
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
The problem is backwards compatibility - old projects need to work with
new version of Django. Do you have some suggestion how we can do something
to this without breaking old installations?
We could probably raise a warning at the least, but actually preventing
the multiloading seems hard...
--
Ticket URL: <https://code.djangoproject.com/ticket/18975#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
