Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[red-knot] remove Type::None in favor of always using Type::Instance(_typeshed_.NoneType) #13670

Open
carljm opened this issue Oct 7, 2024 · 1 comment
Open

[red-knot] remove Type::None in favor of always using Type::Instance(_typeshed_.NoneType) #13670

carljm opened this issue Oct 7, 2024 · 1 comment
Assignees
@MichaReiser
Labels
red-knot Multi-file analysis & type inference

Comments

@carljm
Copy link
Contributor

carljm commented Oct 7, 2024

No description provided.

@carljm carljm added help wanted Contributions especially welcome red-knot Multi-file analysis & type inference labels Oct 7, 2024
@AlexWaygood AlexWaygood changed the title [red-knot] remove Type::None in favor of always using Type::Instance(builtins.NoneType)` [red-knot] remove Type::None in favor of always using Type::Instance(_typeshed_.NoneType) Oct 8, 2024
@AlexWaygood AlexWaygood mentioned this issue Oct 8, 2024
Open
@MichaReiser MichaReiser removed the help wanted Contributions especially welcome label Oct 9, 2024
@MichaReiser MichaReiser self-assigned this Oct 9, 2024
@MichaReiser
Copy link
Member

MichaReiser commented Oct 9, 2024 •
edited
Loading

Related mypy issue python/mypy#11287 (for context)

@MichaReiser MichaReiser mentioned this issue Oct 15, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MichaReiser MichaReiser

Labels
red-knot Multi-file analysis & type inference
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@carljm @MichaReiser