Hugo van Kemenade <hugovk+pyt...@gmail.com> added the comment:
## unittest What's needed to move forward with removing the deprecated aliases? A deprecation warning is shown for `python3 -m unittest test_bar` and `python3 test_bar.py` (tested Python 3.6-3.10). No deprecation warning is shown for `python setup.py test`, however, both setuptools and pytest have deprecated/discouraged `python setup.py test`: https://github.com/pypa/setuptools/pull/1878 https://github.com/pytest-dev/pytest/pull/5546 https://github.com/pytest-dev/pytest/issues/5534 Docs already mention they are deprecated: https://docs.python.org/3/library/unittest.html#deprecated-aliases > At a bare minimum you should list removed features in the 3.9 changelog and > porting guide as "will be removed in 3.10". I would even argue to add > deprecation warnings to the code in 3.9 (with permission from the RM). If the > RM is against deprecation warnings, then it might be good idea to postpone > removal to 3.11. So at this stage (3.10 in RC), do we need to list them in the 3.11 changelog and porting guide as "will be removed in 3.12"? ---------- nosy: +hugovk _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue41165> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
