Context Navigation

Changes between Initial Version and Version 1 of Ticket #27880, comment 8

initial	v1
1		It's not that easy to write library code which supports both code paths. I "complained" to Loïc at DutH 2015 (or something) about the `get_query_set` -> `get_queryset` rename. That one was really hard for third party app maintainers to work around and support all possible combinations given that people are supposed to use subclassing to customize behaviors.
	1	It's not that easy to write library code which supports both code paths. I "complained" to Loïc at DutH 2015 (or something) about the `get_query_set` -> `get_queryset` rename. That one was really hard for third party app maintainers to work around and support all possible combinations given that people are supposed to use subclassing to customize behaviors, even when I agreed with the rename on the basis that `get_queryset` reads better and is more consistent. (That's to say it was a good change.)
2	2
3	3	This seems to be a similar case. It's nice that Python now supports calling this method and that we could in principle use it for our own purposes, but the explicitness of `contribute_to_class` might still have some value. Especially given the fact that the change doesn't allow us to remove a lot of code in the future, and given that it replaces an explicit mechanism with a more implicit mechanism where people have to know more of Python's internals to do what they want.