#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 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
No, the first issue is to determine if we can actually do anything about
this without breaking backwards compat.
We can't raise that error unconditionally. This would break a _lot_ of
existing applications, and while they should probably fix their project,
it isn't something we can enforce them to do. Even going through
deprecation seems hard here, this is not a simple change to do to existing
project. In general I have a feeling we might be deprecating a little too
much stuff, especially taking in account we don't have long-term releases.
But, yeah, if we get two different class instances with same app-
label/model name and same file path that seems to be a sign of
doubleimport...
--
Ticket URL: <https://code.djangoproject.com/ticket/18975#comment:3>
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.
