#22341: Split django.db.models.fields.related into multiple modules.
----------------------------------------------+--------------------
Reporter: loic84 | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Database layer (models, ORM) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
The `django.db.models.fields.related` module is very large and pretty hard
to work with.
It contains a lot of similar concepts with only slight differences, and
one thing can easily be mistaken for its exact opposite, which makes
navigating the file very error-prone. This is made worse by the fact that
some class name are borderline wrong, (e.g.
`ReverseSingleRelatedObjectDescriptor` which actually is the forward FK
descriptor).
Quoting akaariai: "fields/related.py is a brain melting machine".
This ticket proposes that we turn `related.py` into a package with the
following modules: `related_field.py`, `many_to_one.py`, `one_to_one.py`
and `many_to_many.py`.
--
Ticket URL: <https://code.djangoproject.com/ticket/22341>
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/049.534c4b043a4524517c43b5d532f130d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
