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.

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

Introduce NothingType #1358

Merged
merged 10 commits into from
Dec 10, 2024
Merged

Introduce NothingType #1358

merged 10 commits into from
Dec 10, 2024

Conversation

Tinche
Copy link
Member

@Tinche Tinche commented Oct 13, 2024

So I introduced NothingType, but from what I can tell we're not using this anywhere? This is solely for the benefit of third parties annotating their code to accept NOTHING?

@Tinche Tinche linked an issue Oct 13, 2024 that may be closed by this pull request
@hynek
Copy link
Member

hynek commented Oct 14, 2024

I presume this is based on https://discuss.python.org/t/do-we-need-a-valuealias-in-addition-to-typealias/67609? I guess it needs some docs and a changelog entry?

@hynek
Copy link
Member

hynek commented Nov 17, 2024

nudge

@hynek
Copy link
Member

hynek commented Dec 10, 2024

Is there any chance at all to test this??

@Tinche Tinche force-pushed the tin/fix-nothing branch 2 times, most recently from ad225bc to ae4c51d Compare December 10, 2024 09:39
@Tinche Tinche enabled auto-merge December 10, 2024 10:16
@Tinche Tinche added this pull request to the merge queue Dec 10, 2024
Merged via the queue into main with commit d18763c Dec 10, 2024
19 checks passed
@Tinche Tinche deleted the tin/fix-nothing branch December 10, 2024 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

pyright change breaks intended usage of attrs.NOTHING
2 participants