Skip to content
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

Warning message for max_depth does not say where it comes from #8

Closed
frexvahi opened this issue Apr 20, 2018 · 0 comments · Fixed by #10
Closed

Warning message for max_depth does not say where it comes from #8

frexvahi opened this issue Apr 20, 2018 · 0 comments · Fixed by #10

Comments

@frexvahi
Copy link

If the Settings constructor is called on module import then often the logging module has not been set up to show which package has called the logger, so all the user sees is the message:

`max_depth` is deprecated and will be removed in next release. Please use `implicit_depth` instead.

Probably it is better to use warnings.warn instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant