Flesh out the backwards-incompatibility note about indexing Choices.

This commit is contained in:
Carl Meyer 2013-10-11 13:32:07 -06:00
parent 06dddbfa82
commit 907014dab9

View file

@ -10,9 +10,12 @@ master (unreleased)
* `get_subclass()` method is now available on both managers and
querysets. Thanks Travis Swicegood. Merge of GH-82.
* Indexing into a ``Choices`` instance now translates database representations
to human-readable choice names, rather than simply indexing into an array of
choice tuples. (Indexing into ``Choices`` was previously not documented.)
* BACKWARDS-INCOMPATIBLE: Indexing into a ``Choices`` instance now translates
database representations to human-readable choice names, rather than simply
indexing into an array of choice tuples. (Indexing into ``Choices`` was
previously not documented.) If you have code that is relying on indexing or
slicing ``Choices``, the simplest workaround is to change e.g. ``STATUS[1:]``
to ``list(STATUS)[1:]``.
* Fix bug in `InheritanceManager` with grandchild classes on Django 1.6+;
`select_subclasses('child', 'child__grandchild')` would only ever get to the