| 1 | | This is a similar proposal to https://code.djangoproject.com/ticket/31561, but it is not the same. Currently using |
| 2 | | {{{ |
| 3 | | x in myQuerySet |
| 4 | | }}} |
| 5 | | results in python using the fallback solution: https://docs.python.org/3/reference/expressions.html#membership-test-details |
| 6 | | Because https://groups.google.com/g/django-developers/c/NZaMq9BALrs/m/OCNTh6QyCAAJ deiced to implement contains in https://code.djangoproject.com/ticket/24141 |
| 7 | | I think it is only consistent to have the same behavior implemented in `__contains__`. I would expect that, it is also a more efficient implementation and unifies django behavior. Nevertheless, documentation is needed why this inconsistency exists. I was not able to find a reason. Because the mailing list agreed on adding contains, this is discussed behavior. Why was `__contains__` not added in the first place? To not have breaking changes? I cannot see what would break. |
| | 1 | This is a similar proposal to #31561, but it is not the same. Currently using `x in myQuerySet` results in Python using the fallback solution: https://docs.python.org/3/reference/expressions.html#membership-test-details because https://groups.google.com/g/django-developers/c/NZaMq9BALrs/m/OCNTh6QyCAAJ decided to implement contains in #24141. |