Sorry, something went wrong.
|
I am working on a patch which gets rid of uses of obsolete functions. |
Sorry, something went wrong.
|
I had to adapt test_support, since __module__ is now unittest instead of unittest.loader for these three functions. |
Sorry, something went wrong.
There was a problem hiding this comment.
Are all tests warning-free?
If these functions are not used in unittest tests, add special tests, catch DeprecationWarning and check the filename attribute (to ensure that the stacklevel is correct).
Sorry, something went wrong.
| _TextTestResult = TextTestResult | ||
|
|
||
| from .loader import ( | ||
| makeSuite as _makeSuite, |
There was a problem hiding this comment.
Why not add deprecations when they are defined?
Sorry, something went wrong.
There was a problem hiding this comment.
IIUC, it is the "shortcuts" that are deprecated, not the methods themselves. Should I deprecate the undocumented unittest.TestLoader.makeSuite and unittest.TestLoader.findTestCases as well?
Sorry, something went wrong.
There was a problem hiding this comment.
There are no unittest.TestLoader.makeSuite and unittest.TestLoader.findTestCases.
Sorry, something went wrong.
There was a problem hiding this comment.
Sorry, I meant unittest.loader, not unittest.TestLoader:
Sorry, something went wrong.
|
Thanks for reviewing and merging, @serhiy-storchaka and @ambv! |
Sorry, something went wrong.
Scheduled for removal in Python 3.13
https://bugs.python.org/issue5846