You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while we may not want to actually change the behavior (given existing code on the wild might use it, as mentioned in previous discussions), what about raise a warning? Or is that also too intrusive?
Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
The text was updated successfully, but these errors were encountered:
I'd probably be more inclined to document recipes/patterns to achieve the desired result if we need additional materials here since we have already documented that bool() is not recommended as a type converter.
The bool() function is not recommended as a type converter. All it does is convert empty strings to False and non-empty strings to True. This is usually not what is desired.
My concern is that adding a warning here could still break tests, etc.
Feature or enhancement
Proposal:
There has been complaints about
type=bool
usage in argparse: #81745 #83348 #71181 . See also https://stackoverflow.com/questions/15008758/parsing-boolean-values-with-argparsewhile we may not want to actually change the behavior (given existing code on the wild might use it, as mentioned in previous discussions), what about raise a warning? Or is that also too intrusive?
Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
The text was updated successfully, but these errors were encountered: