Fix p* scripts to produce an error when given a bad config_uri #3766
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
This gives coverage 100% coverage. Why this happens I don't know.
|
I have changed the github workflow to get this to pass CI. This change is unrelated to the purpose of the patch. (macos-11 is no longer offered.) |
|
To see what this fixes, try: |
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.
When a bad settings URI (usually a path to a non-existant file) is
supplied to one of pyramid's command line programs, and in general
when there is a reason why a settings file cannot be used, produce
an error message instead of a traceback.
Applications which import pyramid.paster must handle the
plaster.exceptions.PlasterError exception themselves.