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 davin
Recipients davin, docs@python, sbt, td
Date 2015-03-01.22:20:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425248420.9.0.0163247389946.issue23484@psf.upfronthosting.co.za>
In-reply-to
Content
To be fair, the docs in 2.7 do actually mention the use of 'block' instead of 'blocking' in acquire though it does so inside a "Note" block a bit later in the docs after first claiming that multiprocessing.Lock is a "clone".

In 3.4, that important detail has been inexplicably stripped from this distended "Note" block.


Ultimately, this use of the "Note" block seems to misplace important information that should appear in the description of the multiprocessing.Lock class and its siblings in the synchronization section.
History
Date User Action Args
2015-03-01 22:20:20davinsetrecipients: + davin, docs@python, sbt, td
2015-03-01 22:20:20davinsetmessageid: <1425248420.9.0.0163247389946.issue23484@psf.upfronthosting.co.za>
2015-03-01 22:20:20davinlinkissue23484 messages
2015-03-01 22:20:20davincreate