Sebastian Rittau
Sebastian Rittau
Neither #11249, not #11245, the two PRs included in the latest release, *should* have an influence here. I'm not sure what exactly is going on here, but types-protobuf doesn't add...
This problem was introduced by typeshed-internal/stub_uploader#109. Previously, the `google-stubs` directory was missing the `py.typed` file that marked the stubs as partial. I think this was an error according to the...
> If I understand correctly, "google" is a namespace package and the `py.typed` marker should be found in `google-stubs/protobuf/` rather than `google-stubs/` ? (that's what I'm getting from the part...
I'm not sure who has access to the packages on PyPI. I think @ilevkivskyi could do it.
This should now be expressible using `ParamSpec`.
See the test_cases/stdlib directory for examples on how to write tests. Basically, use `typing_extensions.assert_type()` to make sure a type is as expected, and `# type: ignore` for expected failures.
Apart from the necessary stubtest changes (and comment there), could you also add a comment to the stub to explain the situation for posterity?
This has conflicts now.
I'm fine with noqa'ing the warnings in the `CoersiveEnum`s. Maybe even do so for the whole file.
TypeVar defaults are now available in typeshed.