Stubtest: add some hacks so that sys.monitoring
is checked in typeshed's CI
#16269
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.
Currently, in typeshed's CI, stubtest isn't detecting that
sys.monitoring
is missing from typeshed. Even if you addsys.monitoring
stubs to typeshed, stubtest doesn't verify that any of the details aboutsys.monitoring
are correct, sincesys.monitoring
is somewhat unique: it's a genuine instance oftypes.ModuleType
in the global namespace of thesys
module, butimport sys.monitoring
will fail at runtime (sys
isn't a package).I verified locally that these changes cause stubtest to start complaining about
sys.monitoring
being missing with typeshed's current setup; and, if python/typeshed#10890 were merged, these changes here would cause stubtest to start complaining if there were any inaccuracies between the runtime and the stubs forsys.monitoring