Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix #1475 - filter_overrides extra now applied when field has choices #1476

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Spycho
Copy link

@Spycho Spycho commented Feb 9, 2022

Code change compatible with older python versions ({**a, **b} rather than a | b used for combining dictionaries), as I spotted via running tox on your project it wants to run back to 3.6.

Test added for this case, checked it fails without the change, passes with.

Closes #1475

@Spycho
Copy link
Author

Spycho commented May 10, 2022

It would be great to get this merged and released @carltongibson so we can stop depending on my fork.

@carltongibson carltongibson self-requested a review May 10, 2022 18:11
@carltongibson
Copy link
Owner

@Spycho 👍 DF is on the list for a dust-off and release after Django 4.1a1, so I shall give it a look then. Thanks.

@carltongibson
Copy link
Owner

... I spotted via running tox on your project it wants to run back to 3.6.

We'll be dropping support for PY36, and Djangos<3.2 if you fancy making those adjustments? 🙂

@Spycho
Copy link
Author

Spycho commented May 10, 2022

Happy to, but wouldn't it be best to merge this in as is, as it works with all versions, and then refactor to use the new dictionary combining syntax after you've dropped 3.6 support?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

filter_overrides extra is not applied when the field has a choices attribute
2 participants