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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, ocean-city
Date 2008-09-10.12:45:01
SpamBayes Score 9.554943e-06
Marked as misclassified No
Message-id <1221050732.35.0.270706544022.issue3807@psf.upfronthosting.co.za>
In-reply-to
Content
The patch is not easy to read, but if it can be summarized to:

    if sysconfig.get_config_var('WITH_THREAD'):
        <build the _multiprocessing extension>
    else:
        missing.append('_multiprocessing')

then this makes sense - it seems that the multiprocessing module is
completely unusable if python cannot use threads. Even at the python
level, it uses "import threading" in many places.

This need another review, though. Raising issue to ReleaseBlocker.
History
Date User Action Args
2008-09-10 12:45:32amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, ocean-city
2008-09-10 12:45:32amaury.forgeotdarcsetmessageid: <1221050732.35.0.270706544022.issue3807@psf.upfronthosting.co.za>
2008-09-10 12:45:02amaury.forgeotdarclinkissue3807 messages
2008-09-10 12:45:01amaury.forgeotdarccreate