Message 206138 - Python tracker

➜

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	pitrou
Recipients	Olivier.Grisel, brett.cannon, eric.snow, ncoghlan, pitrou, python-dev, sbt
Date	2013-12-13.19:26:27
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1386962787.33.0.718332639183.issue19946@psf.upfronthosting.co.za>
In-reply-to

Content
Let's reopen, shall we? If not for 3.4, at least for 3.5. It's likely that multiprocessing needs a __main__ simply because it needs a way to replicate the parent process' state in the child (for example, the set of imported modules, the logging configuration, etc.). Perhaps Richard can elaborate. But, AFAIU, the __main__ could be imported as a script rather than a "proper" module from sys.path.

Let's reopen, shall we? If not for 3.4, at least for 3.5.

It's likely that multiprocessing needs a __main__ simply because it needs a way to replicate the parent process' state in the child (for example, the set of imported modules, the logging configuration, etc.). Perhaps Richard can elaborate.

But, AFAIU, the __main__ could be imported as a script rather than a "proper" module from sys.path.

History
Date	User	Action	Args
2013-12-13 19:26:27	pitrou	set	recipients: + pitrou, brett.cannon, ncoghlan, python-dev, sbt, eric.snow, Olivier.Grisel
2013-12-13 19:26:27	pitrou	set	messageid: <1386962787.33.0.718332639183.issue19946@psf.upfronthosting.co.za>
2013-12-13 19:26:27	pitrou	link	issue19946 messages
2013-12-13 19:26:27	pitrou	create