Danny Yang
Danny Yang
### Describe the Bug From the typing spec: > The runtime implementation of NamedTuple enforces that fields with default values must come after fields without default values. Type checkers should...
### Describe the Bug https://typing.python.org/en/latest/spec/directives.html#deprecated warn on the following: 1. import deprecated class/function 2. call deprecated function For now, this can be a regular type error since we don't support...
### Describe the Bug https://typing.python.org/en/latest/spec/directives.html#deprecated See parent issue for context. ### Sandbox Link _No response_ ### (Only applicable for extension issues) IDE Information _No response_
### Describe the Bug https://typing.python.org/en/latest/spec/directives.html#deprecated See parent issue for context. ### Sandbox Link _No response_ ### (Only applicable for extension issues) IDE Information _No response_
### Describe the Bug We know what position is associated with each error, why don't we show the source code around that position for each error when Pyrefly is invoked...
This PR clarifies the typing spec around named tuple fields and adds a few conformance test cases: - fields are not being allowed to begin with underscore (and its interaction...
The context is in example 2 from https://github.com/python/typing/pull/1918 It doesn't make sense to enforce this requirement for just `**kwargs` but not any other arguments annotated with a TypedDict, and additionally,...
### Question Hi, I'm following up from [this post](https://discuss.python.org/t/call-for-suggestions-nominate-python-packages-for-typing-improvements/) in the Python Typing forum, where this project was mentioned as a potential area that could benefit from typing investments. I...
We have quite a few good first issue/good second issue's available, and they're being created/solved at a good pace. Excited to keep up the momentum by listing the project here....