#29215: Document potential change to behaviour of QuerySet methods when
upgrading
to Python 3.6
-------------------------------------+-------------------------------------
Reporter: Matt Fisher | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 2.0
Severity: Normal | Resolution:
Keywords: documentation | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
I think the documentation suggests that `.filter(b__in=some_qs, a=1)` is
equivalent to `.filter(a=1, b__in=some_qs)`. I'm not sure if we should
document the subtleties you brought up about the actual SQL that's
produced. I doubt there are any tests for this "feature." If we don't
document it, then documenting a possible change regarding it doesn't make
much sense. Well, it's now informally documented with this ticket.
By the way, we're no longer updating the Django 1.11 documentation, which
includes the "porting to Python 3" document. The Django 1.11 documentation
[https://docs.djangoproject.com/en/1.11/howto/deployment/checklist
/#python-options recommends] using `python -R` for a random hash seed,
when using Python 2.
--
Ticket URL: <https://code.djangoproject.com/ticket/29215#comment:2>
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/068.d45c6f84a649decabcfd67bd7db66d36%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
