Rebecca Chen
Rebecca Chen
See https://github.com/python/typeshed/pull/6585. There are two problems: * pytype chokes on `from ... import X` thanks to https://github.com/google/pytype/blob/002b88cf8e0254fbd73fa0277800ec1d0c4e9a99/pytype/pyi/parser.py#L61. * nested class issues: https://github.com/python/typeshed/pull/6585/commits/c1fe447505ac4303d1eea51374a49d89a65890c1
These are autogenerated files that contain a lot of constructs that questionably belong in stubs; for example, they use `typing.cast` to set some values rather than just declaring that the...
From https://github.com/googleapis/google-cloud-python/pull/6769#issuecomment-443837463. That particular issue hasn't been figured out yet, but it got me to think about whether it's generally possible for pytype to accidentally map two source files to...
PEP: https://www.python.org/dev/peps/pep-0612/ As a simple first step, we should add ParamSpec and Concatenate to the typing stub so typeshed can start using them (https://github.com/python/typeshed/issues/4827).
Type information for third party libraries will start being distributed outside of typeshed per [PEP 561](https://www.python.org/dev/peps/pep-0561/); we should support this.
The following is a common code pattern: ``` try: import foo except ImportError: foo = ``` It's easy enough to add `# pytype: disable=import-error` on the import line, but we...
Users have expressed that they'd prefer to be able to work with pytype in their IDE, rather than switching back and forth to the command line.
It would be useful to have a tool that users could run to generate some information to attach to bug reports: * OS * pytype version * contents of .pytype/...
https://peps.python.org/pep-0692/