#15363: get_queryset & get_query_set
--------------------------------------+------------------------------------
Reporter: sorl | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: 1.3-beta
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 aaugustin):
By now, as far as I can tell, the consensus has shifted towards not making
a break-everything 2.0. I think we can proceed with a regular deprecation
path.
We should normalize towards the non-underscored version: `queryset` and
`get_queryset` because that's the most common way of writing it.
--
Ticket URL: <https://code.djangoproject.com/ticket/15363#comment:5>
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.
For more options, visit https://groups.google.com/groups/opt_out.
