New submission from 徐靖 <shiyucho...@gmail.com>: In https://docs.python.org/3/whatsnew/3.0.html#library-changes Documentation, it said "Cleanup of the thread module: acquire_lock() and release_lock() are gone; use acquire() and release() instead." But in 3.7, I can still find {"acquire_lock", (PyCFunction)(void(*)(void))lock_PyThread_acquire_lock, METH_VARARGS | METH_KEYWORDS, acquire_doc}, in _threadmodule.c line 217, which defined this function. And in my code ,these functions work, without any warning or error. So maybe the Documentation should be changed, or the support of these functions should be removed, or at least add a warning. It has no effect on code, but truly confusing and waste me an hour to search for why.
---------- assignee: docs@python components: Documentation messages: 348053 nosy: docs@python, shiyuchong priority: normal severity: normal status: open title: _thread: acquire_lock,release_lock still in use while declared to be "gone" in Documentation versions: Python 3.7 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37608> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
