Mailman 3 January 2008 - Distutils-SIG

Re: [Distutils] bugfix for GUI.exe launcher
by Phillip J. Eby 03 Jan '08

03 Jan '08

At 02:22 PM 1/3/2008 -0500, Alexander Michael wrote: >I raised this issue in the beginning of December [1]_ but haven't >received a response yet (nor have I seen it corrected in the SVN). I >would like to see this corrected, but I was under the impression that >bug reports for setuptools should be sent to the distutils-sig >mailling list. Do you know how we should next proceed to get this >fixed? I've been having difficulty reproducing the error, so it's hard for me to confirm that the patch fixes it. If somebody wants to extend their patch to include a test that fails on their system without the patch but succeeds with it, I'd be happy to go ahead and include it. See setuptools/tests/win_script_wrapper.txt for the existing test code, which currently only covers the CLI wrapper, not the GUI one.

2 1

bugfix for GUI.exe launcher
by Robin Dunn 03 Jan '08

03 Jan '08

I see in the archives that this has been reported before, and I can verify that the attached patch does fix the problem for me. Basically what is happening is that the launcher is trying to execute python with the "#!" still in the name. I verified this by rebuilding gui.exe without -mwindows arg so it would still be a console app so I would see the failure message. It printed this: "Could not exec #!c:\TOOLS\python25\pythonw.exe" -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! Index: launcher.c =================================================================== --- launcher.c (revision 59634) +++ launcher.c (working copy) @@ -231,8 +231,8 @@ if (is_gui) { /* Use exec, we don't need to wait for the GUI to finish */ - execv(python, (const char * const *)(newargs)); - return fail("Could not exec %s", python); /* shouldn't get here! */ + execv(ptr, (const char * const *)(newargs)); + return fail("Could not exec %s", ptr); /* shouldn't get here! */ } /* We *do* need to wait for a CLI to finish, so use spawn */

2 1

verify status in register.py
by Tarek Ziadé 02 Jan '08

02 Jan '08

Hello I was wondering what is the status of the "--verify" option in register. It looks like it has been deprecated in favor of --dry-run (http://mail.python.org/pipermail/python-checkins/2003-April/035067.html) but I can still see it in the boolean_options in the trunk: http://svn.python.org/view/python/trunk/Lib/distutils/command/register.py?r… Shouldn't it be removed ? Regards Tarek -- View this message in context: http://www.nabble.com/verify-status-in-register.py-tp14579392p14579392.html Sent from the Python - distutils-sig mailing list archive at Nabble.com.

1 0