Skip to content

Only use dataclasses._MISSING_TYPE if it's defined - #578

Open
s-t-e-v-e-n-k wants to merge 1 commit into
lidatong:masterfrom
s-t-e-v-e-n-k:do-not-use-dataclasses-missing-type
Open

Only use dataclasses._MISSING_TYPE if it's defined#578
s-t-e-v-e-n-k wants to merge 1 commit into
lidatong:masterfrom
s-t-e-v-e-n-k:do-not-use-dataclasses-missing-type

Conversation

@s-t-e-v-e-n-k

@s-t-e-v-e-n-k s-t-e-v-e-n-k commented Aug 12, 2026

Copy link
Copy Markdown

Python 3.15 has removed dataclasses._MISSING_TYPE, since it now uses its own built in sentinal type, so make use of it if it's defined, falling back to checking dataclasses.MISSING if it is.

Python 3.15 has removed dataclasses._MISSING_TYPE, since it now uses its
own built in sentinal type, so make use of it if it's defined, falling
back to checking dataclasses.MISSING if it is.
@s-t-e-v-e-n-k
s-t-e-v-e-n-k force-pushed the do-not-use-dataclasses-missing-type branch from 89d2659 to 3e5fd9d Compare August 24, 2026 04:45
@s-t-e-v-e-n-k s-t-e-v-e-n-k changed the title Do not use dataclasses._MISSING_TYPE Only use dataclasses._MISSING_TYPE if it's defined Aug 24, 2026
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.

1 participant