Fix a few issues with parameter defaults #9572
Merged
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.
Some of these vary depending on the machine you're running on (the ones in
sysconfig.pyi
,platform.pyi
,ctypes/__init__.pyi
,multiprocessing/heap.pyi
,pydoc.pyi
). We might be able to give slightly better defaults for some of these if PyCQA/flake8-pyi#336 (or something like it) is merged.Some others currently have integer defaults in the stub, but enum defaults at runtime, causing stubtest to complain if you use mypy
master
(the ones inssl.pyi
,socket.pyi
,asyncore.pyi
).The
email.parser
ones just need some method overrides in the stub that weren't necessary before we added default values.Refs #8988 (comment), and following comments.