[issue41165] [Python 3.10] Remove APIs deprecated long enough

Hugo van Kemenade 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

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Change by Inada Naoki : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue41165] [Python 3.10] Remove APIs deprecated long enough

miss-islington added the comment: New changeset 1ce59f0421d9550762977454bda22db750aa20aa by Miss Islington (bot) in branch '3.9': bpo-41165: Deprecate PyEval_ReleaseLock() (GH-21309) https://github.com/python/cpython/commit/1ce59f0421d9550762977454bda22db750aa20aa --

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +20493 pull_request: https://github.com/python/cpython/pull/21345 ___ Python tracker

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Inada Naoki added the comment: New changeset 9ce8132e1f2339cfe116dfd4795574182c2245b4 by Inada Naoki in branch 'master': bpo-41165: Deprecate PyEval_ReleaseLock() (GH-21309) https://github.com/python/cpython/commit/9ce8132e1f2339cfe116dfd4795574182c2245b4 --

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Karthikeyan Singaravelan added the comment: Adding Miro since Fedora will be testing Python 3.10 and deprecated API removals here might potentially affect libraries like Python 3.9 testing. -- nosy: +hroncok ___ Python tracker

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Change by Inada Naoki : -- keywords: +patch pull_requests: +20461 pull_request: https://github.com/python/cpython/pull/21309 ___ Python tracker ___

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Inada Naoki added the comment: As we discussed in ML, PyEval_ReleaseLock is still used and removing may be not simple. Keep it as-is until Python 4.0. -- ___ Python tracker

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Inada Naoki added the comment: Hmm. You are right. The warnings are shown by default. On the other hand, some project uses custom `setup.py test` command. It hides the DeprecationWarning. https://github.com/warner/python-ed25519/blob/master/setup.py

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Karthikeyan Singaravelan added the comment: > For the record, I noticed DeprecationWarning is not shown by unittest.runner > by default. There is an open issue for this but I think it's enabled by default https://bugs.python.org/issue39892 $ cat /tmp/test_bar.py import unittest import

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Inada Naoki added the comment: I found most of deprecated items in my first comment are aliving by difficult reasons. I grepped top 4000 packages and found some candidates to deprecate. ## turtle * settiltangle is not used anywhere. * tiltangle is also deprecated by docstring, but not in

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Inada Naoki added the comment: For the record, I noticed DeprecationWarning is not shown by unittest.runner by default. For example, https://travis-ci.org/github/necaris/python3-openid/jobs/703119609 So deprecated aliases should be not removed in 3.10. --

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Inada Naoki added the comment: I don't propose adding DeprecationWarning in 3.9 in this issue. I don't propose removing functions that don't emit DeprecationWarning. My first message is just a starting point. I don't propose to remove them all. --

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Christian Heimes added the comment: I'm all in favor to remove deprecated things, but please set a tangible deadline first. A lot of these functions have been deprecated for like a decade. Users tend to forget about deprecations or assume that removal was never going to happen. For example

[issue41165] [Python 3.10] Remove APIs deprecated long enough

Change by Inada Naoki : -- title: [Python 3.10] Remove APIs deprecated since Python 3.3 -> [Python 3.10] Remove APIs deprecated long enough ___ Python tracker ___