[issue22952] multiprocessing doc introduction not in affirmative tone

2015-01-11 Thread Antoine Pitrou
Antoine Pitrou added the comment: I've committed your patches, Davin. Thank you for contributing! -- nosy: +pitrou resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.6 ___ Python tracker

[issue22952] multiprocessing doc introduction not in affirmative tone

2015-01-11 Thread Roundup Robot
Roundup Robot added the comment: New changeset e7d03a33e675 by Antoine Pitrou in branch '2.7': Issue #22952: improve multiprocessing doc introduction and defer notes until appropriate. https://hg.python.org/cpython/rev/e7d03a33e675 -- ___ Python trac

[issue22952] multiprocessing doc introduction not in affirmative tone

2015-01-11 Thread Roundup Robot
Roundup Robot added the comment: New changeset a9a9c71f8e15 by Antoine Pitrou in branch '3.4': Issue #22952: improve multiprocessing doc introduction and defer notes until appropriate. https://hg.python.org/cpython/rev/a9a9c71f8e15 New changeset a65c23ea5f9e by Antoine Pitrou in branch 'default

[issue22952] multiprocessing doc introduction not in affirmative tone

2014-12-23 Thread Raymond Hettinger
Raymond Hettinger added the comment: > Procedural question ... is a fix for this considered an "enhancement"? Improvements to documentation are almost always backported. The contrasts with code changes where enhancements (new features, optimizations, or refactorings) are made only on the late

[issue22952] multiprocessing doc introduction not in affirmative tone

2014-12-22 Thread Davin Potts
Davin Potts added the comment: Procedural question (wanting to understand the label given to this issue): when documentation does not adhere to the Python Developer's Guide, is a fix for this considered an "enhancement"? -- versions: +Python 3.6 __

[issue22952] multiprocessing doc introduction not in affirmative tone

2014-11-26 Thread Raymond Hettinger
Raymond Hettinger added the comment: +1 It looks like the relevant information has been preserved while adding an example where the module is being used as designed. -- ___ Python tracker _

[issue22952] multiprocessing doc introduction not in affirmative tone

2014-11-26 Thread Davin Potts
Changes by Davin Potts : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue22952] multiprocessing doc introduction not in affirmative tone

2014-11-26 Thread Berker Peksag
Changes by Berker Peksag : -- nosy: +sbt stage: -> patch review type: behavior -> enhancement versions: +Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker ___ __

[issue22952] multiprocessing doc introduction not in affirmative tone

2014-11-26 Thread Davin Potts
Davin Potts added the comment: Attached is a proposed patch for the 3.4 branch. The same modifications are made in this patch as in the patch for the 2.7 branch, with two minor tweaks: 1) The affirmative tone example uses Pool in a with statement as is supported since 3.3. 2) References in the

[issue22952] multiprocessing doc introduction not in affirmative tone

2014-11-26 Thread Davin Potts
Davin Potts added the comment: 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

[issue22952] multiprocessing doc introduction not in affirmative tone

2014-11-26 Thread Davin Potts
New submission from Davin Potts: The introduction section of the multiprocessing module's documentation does not adhere to the python dev guidelines for keeping things in the affirmative tone. Problem description: Specifically, the intro section contains a warning block that, while conveying s