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
Date 2014-11-26.21:45:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1417038308.85.0.925512024605.issue22952@psf.upfronthosting.co.za>
In-reply-to
Content
Attached is a proposed patch for the 2.7 branch.

It provides 2 changes to the documentation:
1) Moves the warning text block regarding synchronization functionality not necessarily being available on all systems to the "Synchronization between processes" section (Section 16.6.1.3 in the 2.7 docs).
2) Adds a paragraph introducing (in the affirmative tone) a good/common practice as shown in a working example to drive home the key point about importability by subprocesses.  The original example of what not to do has been preserved by moving it to the "Using a pool of workers" section (Section 16.6.1.5 in the 2.7 docs).

Note that this patch does not attempt to resolve the issue of :class:`Pool` not being resolved by Sphinx to properly point at the multiprocessing.pool.Pool class description.  This issue appears addressed in the 3.4 docs but not in some other branches.
History
Date User Action Args
2014-11-26 21:45:08davinsetrecipients: + davin, docs@python
2014-11-26 21:45:08davinsetmessageid: <1417038308.85.0.925512024605.issue22952@psf.upfronthosting.co.za>
2014-11-26 21:45:08davinlinkissue22952 messages
2014-11-26 21:45:08davincreate