Message 364487 - 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	vstinner
Recipients	vstinner
Date	2020-03-17.23:39:02
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1584488342.57.0.981206411156.issue39998@roundup.psfhosted.org>
In-reply-to

Content
The PyEval_AcquireLock() and PyEval_ReleaseLock() functions are misleading and deprecated since Python 3.2. bpo-10913 deprecated them: commit 5ace8e98da6401827f607292a066da05df3ec5c1 Author: Antoine Pitrou <solipsis@pitrou.net> Date: Sat Jan 15 13:11:48 2011 +0000 Issue #10913: Deprecate misleading functions PyEval_AcquireLock() and PyEval_ReleaseLock(). The thread-state aware APIs should be used instead. It's now time to remove them! I discovered these functions while working on bpo-39984. Previously, I never ever used them nor really see them. I only made refactoring them in their code, without paying attention to them.

The PyEval_AcquireLock() and PyEval_ReleaseLock() functions are misleading and deprecated since Python 3.2.

bpo-10913 deprecated them:

commit 5ace8e98da6401827f607292a066da05df3ec5c1
Author: Antoine Pitrou <solipsis@pitrou.net>
Date:   Sat Jan 15 13:11:48 2011 +0000

    Issue #10913: Deprecate misleading functions PyEval_AcquireLock() and
    PyEval_ReleaseLock().  The thread-state aware APIs should be used instead.

It's now time to remove them!

I *discovered* these functions while working on bpo-39984. Previously, I never ever used them nor really see them. I only made refactoring them in their code, without paying attention to them.

History
Date	User	Action	Args
2020-03-17 23:39:02	vstinner	set	recipients: + vstinner
2020-03-17 23:39:02	vstinner	set	messageid: <1584488342.57.0.981206411156.issue39998@roundup.psfhosted.org>
2020-03-17 23:39:02	vstinner	link	issue39998 messages
2020-03-17 23:39:02	vstinner	create