On 06/05/2018 07:54 AM, Tom Forbes wrote:
Are the proposed modifications to how Django runs sensible?
I had a few random thoughts while reading your proposal:
I think getting rid of the related field references could be a big issue
here and cause a lot of headaches for existing applications. Could we do
this in a backwards compatible way at all? I wonder if PEP 567
<https://www.python.org/dev/peps/pep-0567/> could help here, could we
define some kind of ‘Django async context’ and do different things
depending on if this is true or false?
One thought about the related field stuff... whilst having it makes it
easy to get started, any site at scale will sensibly obviate their need
in almost all cases by using select_related, for performance reasons.
--
C
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/4447805e-f035-8242-957e-ffb1e0c57d51%40tinbrain.net.
For more options, visit https://groups.google.com/d/optout.
