[Python-3000] the future of the GIL (original) (raw)
Giovanni Bajo rasky at develer.com
Sat May 12 02:58:58 CEST 2007
- Previous message: [Python-3000] the future of the GIL
- Next message: [Python-3000] the future of the GIL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10/05/2007 3.24, Greg Ewing wrote:
using multiple processes cause some headaches with frozen distributions (PyInstaller, py2exe, etc.), like those usually found on Windows, specifically because Windows does not have fork(). Isn't that just a problem with Windows generally? I don't see what the method of packaging has to do with it.
The processing module has two ways of creating a new process which executes the same program of the current process:
- fork
- the moral equivalent of popen(sys.executable sys.argv[0]) + some magic values passed on the command line which is a pickled state.
The second method doesn't work out-of-the-box when the program is packaged, and it is the only one available in Windows.
Giovanni Bajo Develer S.r.l. http://www.develer.com
- Previous message: [Python-3000] the future of the GIL
- Next message: [Python-3000] the future of the GIL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]