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
gh-60203: Always pass True/False as boolean arguments in tests #99983
Conversation
Unless we explicitly test non-bool values.
|
Thanks @serhiy-storchaka for the PR |
|
Sorry, @serhiy-storchaka, I could not cleanly backport this to |
|
GH-99986 is a backport of this pull request to the 3.11 branch. |
…ythonGH-99983) Unless we explicitly test non-bool values. (cherry picked from commit 76f43fc) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
… tests (pythonGH-99983) Unless we explicitly test non-bool values.. (cherry picked from commit 76f43fc) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
GH-99989 is a backport of this pull request to the 3.10 branch. |
) Unless we explicitly test non-bool values. (cherry picked from commit 76f43fc) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
Unless we explicitly test non-bool values.