[issue3256] Multiprocessing docs are not 3.0-ready

Georg Brandl <[EMAIL PROTECTED]> added the comment: The docstrings are now fixed too. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3256] Multiprocessing docs are not 3.0-ready

Andrii V. Mishkovskyi <[EMAIL PROTECTED]> added the comment: OK, I'll work on this too. :) Patch should be ready by Monday. ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3256] Multiprocessing docs are not 3.0-ready

Jesse Noller <[EMAIL PROTECTED]> added the comment: that's your call Andrii ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list maili

[issue3256] Multiprocessing docs are not 3.0-ready

Andrii V. Mishkovskyi <[EMAIL PROTECTED]> added the comment: btw, some of the docstrings are also outdated, e.g. Pool.imap, Pool.map, etc. Should I handle this one too? ___ Python tracker <[EMAIL PROTECTED]> _

[issue3256] Multiprocessing docs are not 3.0-ready

Andrii V. Mishkovskyi <[EMAIL PROTECTED]> added the comment: Here is the updated version of multiprocessing.rst patch. Not much has changes, as you can see (if you've seen the previous version, of course ;) ). I have only one question left about multiprocessing.rst, it's about 'allow_connection_p

[issue3256] Multiprocessing docs are not 3.0-ready

Changes by Andrii V. Mishkovskyi <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10960/issue3256.multiprocessing.rst.diff ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3256] Multiprocessing docs are not 3.0-ready

Changes by Andrii V. Mishkovskyi <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10848/multiprocessing.rst.diff ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3256] Multiprocessing docs are not 3.0-ready

Andrii V. Mishkovskyi <[EMAIL PROTECTED]> added the comment: OK, then ignore the previous email, I'll send you a new one, with updated questions. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3256] Multiprocessing docs are not 3.0-ready

Jesse Noller <[EMAIL PROTECTED]> added the comment: Thanks - sorry I didn't reply to the mail yet, had to deal with some other stuff first, I should be freed up tonight ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3256] Multiprocessing docs are not 3.0-ready

Andrii V. Mishkovskyi <[EMAIL PROTECTED]> added the comment: And this patch is for Doc/library/multiprocessing.rst. Still, there are lot of issues, and as you none of you (Jesse or Richard) answered my email, I'll post them tomorrow here. Right now, the patch. :) Added file: http://bugs.python.o

[issue3256] Multiprocessing docs are not 3.0-ready

Andrii V. Mishkovskyi <[EMAIL PROTECTED]> added the comment: So, after 5 days of silence I present my current status on the patch. This patch fixes Doc/includes/mp_*.py examples, except for the fact that I couldn't make mp_distributing.py work, but I'm still working on this issue. -- key

[issue3256] Multiprocessing docs are not 3.0-ready

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: georg.brandl -> jnoller ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Py

[issue3256] Multiprocessing docs are not 3.0-ready

Jesse Noller <[EMAIL PROTECTED]> added the comment: If you're willing to make the patch - I can review and submit. I appreciate it ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3256] Multiprocessing docs are not 3.0-ready

New submission from Andrii V. Mishkovskyi <[EMAIL PROTECTED]>: Multiprocessing docs contain examples, that are not valid py3k code, mostly because of print used as a statement. Example (taken from multiprocessing.rst): from multiprocessing import Process def f(name): print 'hello', name if