Skip to content

Better warnings#838

Merged
blink1073 merged 8 commits intoipython:mainfrom
NickCrews:better-warnings
Apr 7, 2023
Merged

Better warnings#838
blink1073 merged 8 commits intoipython:mainfrom
NickCrews:better-warnings

Conversation

@NickCrews
Copy link
Contributor

Fixes #837

NickCrews and others added 6 commits March 20, 2023 13:46
per https://docs.python.org/3/library/warnings.html#warning-categories,
FutureWarnings are intended for end users, and DeprecationWarnings are for
programmers. We are targetting programmers here. 

This is a step towards fixing
ipython#837
this is private and unused.
Copy link
Contributor

@blink1073 blink1073 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@blink1073 blink1073 changed the title Better warnings Better warnings (#838)Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Steven Silvester <steven.silvester@ieee.org> Apr 7, 2023
@blink1073 blink1073 merged commit 5cbf807 into ipython:main Apr 7, 2023
@blink1073 blink1073 changed the title Better warnings (#838)Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Steven Silvester <steven.silvester@ieee.org> Better warnings Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: use of warnings.warn() does not always include stacklevel

2 participants