multi-core Windows 7 box spawns multiple GUIs, from built distribution only

wxPython Users
1

Hello,

My wx app runs as expected from the command line on all platforms.

But it spawns multiple GUIs when running certain multi-core optional routines from a distribution built for Windows OS. I build it with bdist_wininst and package it with InnoSetup.

I’ve attached my “main”. The def main() was added as a possible solution, but does not address this problem. The original calls are commented out in the "if name "… clause.

I’m happy to provide more information if needed. Have you run across this issue?

Thanks,

Phil

GeoDaSpace.py (1.36 KB)

2

Hello,

My wx app runs as expected from the command line on all platforms.

But it spawns multiple GUIs when running certain multi-core optional routines from a distribution built for Windows OS. I build it with bdist_wininst and package it with InnoSetup.

Are those multi-core routines using the multiprocessing module? If so, you probably want to call multiprocessing.freeze_support() at the very start of your script. You have to do this before anything else imports multiprocessing I believe, and it doesn’t hurt to call it even if you’re not running ‘frozen’.

Regards,

Kevin

···

On Aug 6, 2013, at 10:52 AM, Philip Stephens wrote:

I’ve attached my “main”. The def main() was added as a possible solution, but does not address this problem. The original calls are commented out in the "if name "… clause.

I’m happy to provide more information if needed. Have you run across this issue?

Thanks,

Phil

–

You received this message because you are subscribed to the Google Groups “wxPython-users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

<GeoDaSpace.py>

3

Hello,

My wx app runs as expected from the command line on all platforms.

But it spawns multiple GUIs when running certain multi-core optional routines from a distribution built for Windows OS. I build it with bdist_wininst and package it with InnoSetup.

Regards,

Kevin

Are those multi-core routines using the multiprocessing module? If so, you probably want to call multiprocessing.freeze_support() at the very start of your script. You have to do this before anything else imports multiprocessing I believe, and it doesn’t hurt to call it even if you’re not running ‘frozen’.

Yes, we are using the multiprocessing module, and your solution works. Thank you so much for responding!

Best,

Phil

···

On Tuesday, August 6, 2013 11:31:13 AM UTC-7, kevin...@theolliviers.com wrote:

On Aug 6, 2013, at 10:52 AM, Philip Stephens wrote:

I’ve attached my “main”. The def main() was added as a possible solution, but does not address this problem. The original calls are commented out in the "if name "… clause.

I’m happy to provide more information if needed. Have you run across this issue?

Thanks,

Phil

–

You received this message because you are subscribed to the Google Groups “wxPython-users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-user...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

<GeoDaSpace.py>