[issue9843] imp documentation redundancy with acquire_lock and release_lock
New submission from Demur Rumed junkm...@hotmail.com: 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 -- assignee: d...@python components: Documentation messages: 116267 nosy: d...@python, serprex priority: normal severity: normal status: open title: imp documentation redundancy with acquire_lock and release_lock ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9843 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9843] imp documentation redundancy with acquire_lock and release_lock
Benjamin Peterson benja...@python.org added the comment: r84754 -- nosy: +benjamin.peterson resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9843 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9843] imp documentation redundancy with acquire_lock and release_lock
Demur Rumed junkm...@hotmail.com added the comment: That doesn't appear to remove the repetition of their listing. Something I failed to mention: The duplication occurs after imp.reload -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9843 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com