[docs] [multiprocessing] Doc is outdated regarding method picklability (issue 27221)
berker.peksag at gmail.com
berker.peksag at gmail.com
Tue Jun 7 03:35:10 EDT 2016
http://bugs.python.org/review/27221/diff/17535/Doc/library/multiprocessing.rst
File Doc/library/multiprocessing.rst (right):
http://bugs.python.org/review/27221/diff/17535/Doc/library/multiprocessing.rst#newcode2736
Doc/library/multiprocessing.rst:2736: Before version 3.5, bound or
unbound methods could not be used directly
indendation is wrong here
.. versionchanged:: 3.5
Foo bar ...
http://bugs.python.org/review/27221/diff/17535/Doc/library/multiprocessing.rst#newcode2736
Doc/library/multiprocessing.rst:2736: Before version 3.5, bound or
unbound methods could not be used directly
"Before version 3.5," doesn't seem to be necessary.
``.. versionchanged:: 3.5`` will be rendered as "Changed in version
3.5:" so the sentence could be changed to match that.
http://bugs.python.org/review/27221/diff/17535/Doc/library/multiprocessing.rst#newcode2736
Doc/library/multiprocessing.rst:2736: Before version 3.5, bound or
unbound methods could not be used directly
AFAIK there are no unbound methods in Python 3 anymore.
http://bugs.python.org/review/27221/diff/17535/Doc/library/multiprocessing.rst#newcode2737
Doc/library/multiprocessing.rst:2737: as the ``target`` (unless you used
the *fork* start method), because they
``target`` -> *target*
http://bugs.python.org/review/27221/
More information about the docs
mailing list