SelectField will throw ValueError when using list of strings #598
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This may assist with #464 (at least the behavior described by @ftm in that ticket.)
In the validation phase, we use iter_choices now instead of trying to iterate on choices directly. This will mean that regardless of list of tuples or the shortcut list of strings, we always have 3 values when we iterate the list. We use the match result from iter_choices instead of doing the comparison again to save the operation.
If you are using the shortcut list of strings and getting
'too many values to unpack (expected 2)'
, this is the fix.I'm doing the following to work around this right now:
list(zip(
is required to preventchoices
from being an iterator.listTimezones()
is a singleton function that returns a cached list of strings. Without thelist(zip(
or this patch, this will will always fail to validate.