Mark constructor parameters of exceptions as positional-only #1699
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Summary
As these exceptions also inherit from
ValueError
, providing keyword arguments fails when thesuper().__new__
call is performed (ValueError
only takes positional arguments). Generally, I also tend to enforce pos-only args for exceptions, otherwise the default repr doesn't show the argument:Also clean up the stub file a bit: avoid duplicating
__new__
and__init__
(at runtime,__new__
is the one actually defined but it doesn't play well with mkdocstrings), unify docstrings in classes.Fixes pydantic/pydantic#10604.
Related issue number
Checklist
pydantic-core
(except for expected changes)