Skip to content
This repository has been archived by the owner on Nov 3, 2023. It is now read-only.

Switched logging.warn to logging.warning #3569

Merged
merged 2 commits into from Apr 2, 2021
Merged

Conversation

AlexAzaFB
Copy link
Contributor

@AlexAzaFB AlexAzaFB commented Apr 2, 2021

Patch description
Currently there are two ways to log warnings: logging.warn() and logging.warning().
This PR switches all logging.warn() usages to logging.warning() and removes logging.warn() implementation.
Besides removing ambiguity, this change is also inline with Python 3.3 warn vs warning naming.

Testing steps
Unit tests.

Copy link
Contributor

@stephenroller stephenroller left a comment

Choose a reason for hiding this comment

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

Can we keep the logging.warn as available in the library for now, and upgrade it to call logging.warning? There are some external customers that may still be using it.

Also please upgrade the call to logging.warn in logging.py.

Copy link
Contributor

@stephenroller stephenroller left a comment

Choose a reason for hiding this comment

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

Great, thanks for doing this! Looks perfect.

@stephenroller
Copy link
Contributor

The segfault in gpu tests isn't related, but hold on merging a bit please.

@stephenroller
Copy link
Contributor

Actually your branch is from an old parent (np) so this isn't unexpected. You're good to merge whenever.

@AlexAzaFB AlexAzaFB merged commit 56b8309 into master Apr 2, 2021
@AlexAzaFB AlexAzaFB deleted the RemoveLoggingWarn branch April 2, 2021 17:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants