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.

classification
Title: imp documentation redundancy with acquire_lock and release_lock
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: docs@python Nosy List: benjamin.peterson, docs@python, serprex
Priority: normal Keywords:

Created on 2010-09-13 01:22 by serprex, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg116267 - (view) Author: Demur Rumed (serprex) Date: 2010-09-13 01:22
http://docs.python.org/dev/library/imp.html

acquire_lock and release_lock are listed twice. The first iteration of acquire_lock repeats "On platforms without threads, this function does nothing." twice and advises release, while the latter does not
msg116268 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2010-09-13 01:26
r84754
msg116269 - (view) Author: Demur Rumed (serprex) Date: 2010-09-13 01:31
That doesn't appear to remove the repetition of their listing. Something I failed to mention: The duplication occurs after imp.reload
History
Date User Action Args
2022-04-11 14:57:06adminsetgithub: 54052
2010-09-13 01:31:40serprexsetmessages: + msg116269
2010-09-13 01:26:58benjamin.petersonsetstatus: open -> closed

nosy: + benjamin.peterson
messages: + msg116268

resolution: fixed
2010-09-13 01:22:03serprexcreate