Thomas Heller wrote:
Jesse Noller schrieb:
On Fri, May 30, 2008 at 2:19 AM, Farshid Lashkari firstname.lastname@example.org wrote:
On Wed, May 28, 2008 at 10:03 AM, Jesse Noller email@example.com wrote:
I would like to renew the discussion now that "there is a PEP" to see if there are any outstanding things people would like to get resolved. I chose to continue to push it for 2.6 / 3.0 inclusion due to feedback both here and elsewhere that people would rather see this in sooner in some form, rather than later (i.e.: 2.7/3.1). I'm not sure if this is a big issue, but I just tested the module with an application that embeds Python and it doesn't work properly. Instead of spawning worker threads using python.exe, it attempts to use the application. Does the processing module allow specifying the exe to use for spawning worker threads? I would definitely like to see this included in the next release, and having support for embedded Python interpreters would be a big plus.
Let's take this off-list Farshid - but I would like to know more about your application (I'm not up to speed with embedding python in other applications) so I can either add it to the PEP or discuss how best to address this within the module itself.
This may be an issue for py2exe users as well. Please keep me informed (or is there a pyprocessing mailing list where this is discussed?).
py2exe is explicitly supported (via the freezeSupport() call). That may work for the embedded case as well, or it may be something that can be addressed by modifying sys.executable.