feat: all_errors #170
Merged
feat: all_errors #170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
henryiii
force-pushed
the
henryiii/feat/multierror
branch
4 times, most recently
from
6d7997b to
13489c3
Compare
henryiii
force-pushed
the
henryiii/feat/multierror
branch
from
c146bd0 to
f55bd4b
Compare
Signed-off-by: Henry Schreiner <[email protected]>
henryiii
force-pushed
the
henryiii/feat/multierror
branch
from
f55bd4b to
3af5e90
Compare
Signed-off-by: Henry Schreiner <[email protected]>
henryiii
force-pushed
the
henryiii/feat/multierror
branch
from
638be07 to
4dafe4d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Close #45. Adds an
all_errorsparameter that causes all errors to be collected and shown in a ExceptionGroup. The output is a bit ugly for <3.11, but no dependency is required. A build backend can use the backport by replacingpyproject_metadata.errors.ExceptionGroup.If we submit to packaging, this would be the default there #140. And if we do, then I'd be very likely to want the back port here eventually, since a user can use packaging if they need minimal deps. Though, "eventually" probably would be around the time 3.11 becomes the minimum... so yeah, might not happen.
I've also added quite a few missing
key=params as well as provided better descriptions in a few cases.