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 vinay.sajip
Recipients amaury.forgeotdarc, benjamin.peterson, gvanrossum, pjenvey, vinay.sajip
Date 2009-10-14.10:00:37
SpamBayes Score 2.0749487e-05
Marked as misclassified No
Message-id <494201.62032.qm@web25805.mail.ukl.yahoo.com>
In-reply-to <1255509508.73.0.982265302828.issue7120@psf.upfronthosting.co.za>
Content
> Whatever the value of logMultiprocessing is, I suggest to not import the

> multiprocessing module if the application did not import it before:
> something like:
> 
>     if "multiprocessing" in sys.modules:
>         from multiprocessing import current_process
>         self.processName = current_process().name
>     else:
>         # current_process().name returns this the first time
>         self.processName = 'MainProcess'
> 

I suggested "None" because that was the value used in r70348 when logMultipocessing is False. I presume you're only talking about when it's True? I'm confused by your "Whatever the value of logMultiprocessing is, ...".

Should the system behaviour really change depending on whether multiprocessing was already imported? I can see why you're suggesting it but it makes me a little uneasy :-S
History
Date User Action Args
2009-10-14 10:00:40vinay.sajipsetrecipients: + vinay.sajip, gvanrossum, amaury.forgeotdarc, pjenvey, benjamin.peterson
2009-10-14 10:00:38vinay.sajiplinkissue7120 messages
2009-10-14 10:00:37vinay.sajipcreate