-
Notifications
You must be signed in to change notification settings - Fork 14
Exempt adding Type and Value Errors from BC break policy #27
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -86,6 +86,12 @@ The following are **not considered** BC breaks: | |
| choosing new names, but SHOULD NOT pick significantly worse names purely to | ||
| reduce conflict risk. | ||
|
|
||
| - Adding TypeError and ValueError exceptions to validate inputs to functions | ||
| and methods. These are not classified as BC breaks because not adding them | ||
| allows incorrect code to run and thus leads to hard to debug code. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
IMO this wording is not great. Maybe:
|
||
|
|
||
| - Changing the wording of diagnostic, error, or exception messages. | ||
|
|
||
| - Behavior changes in undefined or undocumented edge cases MAY be allowed if | ||
| well justified. However, care SHOULD be taken to minimize disruption. | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add hyphens to turn the adjective phrase into a compound word, increasing readability.