#24317: Deprecate field.rel, replace it with real field instances
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: auvipy
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
The advice I can give is that you should:
1. Find places where rield.remote_field responds to different API than
Field.
2. Fix these one at a time while trying to have backwards compat, even
if the API isn't public.
In addition, simplifications to the APIs are welcome, as is a high level
documentation of how related fields actually work.
We need to try to keep backwards compat as many projects are forced to use
the private APIs.
But most of all, do small incremental changes.
--
Ticket URL: <https://code.djangoproject.com/ticket/24317#comment:9>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.74c7e58e17dcca4b9422b16f25d40738%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
