Message 399825 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	hugovk
Recipients	christian.heimes, hroncok, hugovk, methane, miss-islington, xtreak
Date	2021-08-18.09:27:28
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1629278848.26.0.534758749013.issue41165@roundup.psfhosted.org>
In-reply-to

Content
## 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"?

## 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"?

History
Date	User	Action	Args
2021-08-18 09:27:28	hugovk	set	recipients: + hugovk, christian.heimes, methane, hroncok, miss-islington, xtreak
2021-08-18 09:27:28	hugovk	set	messageid: <1629278848.26.0.534758749013.issue41165@roundup.psfhosted.org>
2021-08-18 09:27:28	hugovk	link	issue41165 messages
2021-08-18 09:27:28	hugovk	create