#22341: Split django.db.models.fields.related into multiple modules.
-------------------------------------+-------------------------------------
Reporter: loic84 | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: 1.8-alpha | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by loic):
Hi @e0ne, I'm still planning to tackle this once I return from holiday. I
discussed this recently on IRC and it'll go further than just splitting
the files:
- Refactor ``ForeignObject`` to not depend on
``ReverseSingleRelatedObjectDescriptor``, which includes factoring out the
relevant bits of ``ReverseSingleRelatedObjectDescriptor`` into a new
descriptor.
- Move the existing ``ReverseSingleRelatedObjectDescriptor`` to
``many_to_one.py`` but deprecate it and introduce a new better named
descriptor, since this is actually the forward side of a FK.
--
Ticket URL: <https://code.djangoproject.com/ticket/22341#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.3d141f88cfbc7fb5c26722f758736a83%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
