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 Stanislaw Izaak Pitucha
Recipients Stanislaw Izaak Pitucha, davin
Date 2015-09-11.02:27:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441938442.72.0.635684206368.issue25053@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with what you said mostly. I wonder though if the message could be clearer in the docs. I remember that the rule about the module being importable without side-effects, but didn't even consider that for the interactive session.

If I understand your analysis correctly, you're basically saying that "don't use multiprocessing" could be a general rule for interactive interpreters? Which would also affect any ipython session like ipython notebooks? (seems to be confirmed if you google for "multiprocessing ipython crash"...) If that's true, maybe that specific case should be spelled out in the docs more explicitly.
History
Date User Action Args
2015-09-11 02:27:22Stanislaw Izaak Pituchasetrecipients: + Stanislaw Izaak Pitucha, davin
2015-09-11 02:27:22Stanislaw Izaak Pituchasetmessageid: <1441938442.72.0.635684206368.issue25053@psf.upfronthosting.co.za>
2015-09-11 02:27:22Stanislaw Izaak Pituchalinkissue25053 messages
2015-09-11 02:27:22Stanislaw Izaak Pituchacreate