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
Remove custom rule for deprecation warnigns in __main__ #11333
Comments
Hi, Are there any news on this issue? Was there any pull request already made? |
I don't believe any pull request was made. Feel free to take it. |
Thank you! I'm reading the links you sent and will come back soon with updates. |
I believe that I have a Pull Request already, however I have some doubts about the project's code and haven't ran any tests. Should I make it anyway and discuss it in the PR? Or should we solve it here? I simply added the if sys.info_version < (3,7): mentioned above on the init_deprecation_warnings() functions in the main IPython class. What i understood is that this issue is fixed for python 3.7 but not for older versions, so I guessed this should suffice. I wanted opinions from more experienced developers in this project to help to check it and to test it. (I made the PR anyway, I saw in Contributing.md that any PR should be done as soon as there is code to discuss) |
Yes, that is the right thing to do. You can run test locally with Thanks, I'll have a look at the PR. |
The code is now conditionally run on < 3.7 (see #11396), once Python 3.6 is dropped this can actually be removed. |
Thanks @LucianaMarques ! |
See https://www.python.org/dev/peps/pep-0565/ we might be able to remove some custom code on 3.7+ and/or have a behavior which is closer to what is defined in the pep.
[EDIT]
This code is now conditionally run on < 3.7 (see #11396), once Python 3.6 is dropped this can actually be removed.
The text was updated successfully, but these errors were encountered: