On Jan 3, 2008 4:12 PM, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> 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.
I've added a test for the GUI wrapper to the referenced file, which I've
attached. Running doctest in verbose mode on it produces:
**********************************************************************
File "win_script_wrapper.txt", line 129, in win_script_wrapper.txt
Failed example:
print output.read()
Expected:
<BLANKLINE>
Got:
Could not exec #!C:\Python25\python.exe
**********************************************************************
File "win_script_wrapper.txt", line 131, in win_script_wrapper.txt
Failed example:
print open(os.path.join(sample_directory, 'test_output.txt'), 'rb').read()
Exception raised:
Traceback (most recent call last):
File "C:\Python25\lib\doctest.py", line 1212, in __run
compileflags, 1) in test.globs
File "<doctest win_script_wrapper.txt[25]>", line 1, in <module>
print open(os.path.join(sample_directory, 'test_output.txt'),
'rb').read()
IOError: [Errno 2] No such file or directory:
'c:\\docume~1\\alex\\locals~1\\temp\\tmpccuxgd\\test_output.txt'
**********************************************************************
1 items had failures:
2 of 28 in win_script_wrapper.txt
***Test Failed*** 2 failures.
This test passes with the modifications:
*** launcher.c.orig Thu Jan 3 17:19:54 2008
--- launcher.c Tue Dec 18 09:37:21 2007
*************** int run(int argc, char **argv, int is_gu
*** 231,238 ****
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! */
}
/* We *do* need to wait for a CLI to finish, so use spawn */
--- 231,238 ----
if (is_gui) {
/* Use exec, we don't need to wait for the GUI to finish */
! 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 */
Thank you!
Alex
Python Script Wrapper for Windows
=================================
setuptools includes wrappers for Python scripts that allows them to be
executed like regular windows programs. There are 2 wrappers, once
for command-line programs, cli.exe, and one for graphica programs,
gui.exe. These programs are almost identical, function pretty much
the same way, and are generated from the same source file. In this
document, we'll demonstrate use of the command-line program only. The
wrapper programs are used by copying them to the directory containing
the script they are to wrap and with the same name as the script they
are to wrap. In the rest of this document, we'll give an example that
will illustrate this.
Let's create a simple script, foo-script.py:
>>> import os, sys, tempfile
>>> from setuptools.command.easy_install import nt_quote_arg
>>> sample_directory = tempfile.mkdtemp()
>>> open(os.path.join(sample_directory, 'foo-script.py'), 'w').write(
... """#!%(python_exe)s
... import sys
... input = repr(sys.stdin.read())
... print sys.argv[0][-14:]
... print sys.argv[1:]
... print input
... if __debug__:
... print 'non-optimized'
... """ % dict(python_exe=nt_quote_arg(sys.executable)))
Note that the script starts with a Unix-style '#!' line saying which
Python executable to run. The wrapper will use this to find the
correct Python executable.
We'll also copy cli.exe to the sample-directory with the name foo.exe:
>>> import pkg_resources
>>> open(os.path.join(sample_directory, 'foo.exe'), 'wb').write(
... pkg_resources.resource_string('setuptools', 'cli.exe')
... )
When the copy of cli.exe, foo.exe in this example, runs, it examines
the path name it was run with and computes a Python script path name
by removing the '.exe' suffic and adding the '-script.py' suffix. (For
GUI programs, the suffix '-script-pyw' is added.) This is why we
named out script the way we did. Now we can run out script by running
the wrapper:
>>> import os
>>> input, output =
os.popen4('"'+nt_quote_arg(os.path.join(sample_directory, 'foo.exe'))
... + r' arg1 "arg 2" "arg \"2\\\"" "arg 4\\" "arg5 a\\b"')
>>> input.write('hello\nworld\n')
>>> input.close()
>>> print output.read(),
\foo-script.py
['arg1', 'arg 2', 'arg "2\\"', 'arg 4\\', 'arg5 a\\\\b']
'hello\nworld\n'
non-optimized
This example was a little pathological in that it exercised windows
(MS C runtime) quoting rules:
- Strings containing spaces are surrounded by double quotes.
- Double quotes in strings need to be escaped by preceding them with
back slashes.
- One or more backslashes preceding double quotes quotes need to be
escaped by preceding each of them them with back slashes.
Specifying Python Command-line Options
--------------------------------------
You can specify a single argument on the '#!' line. This can be used
to specify Python options like -O, to run in optimized mode or -i
to start the interactive interpreter. You can combine multiple
options as usual. For example, to run in optimized mode and
enter the interpreter after running the script, you could use -Oi:
>>> open(os.path.join(sample_directory, 'foo-script.py'), 'w').write(
... """#!%(python_exe)s -Oi
... import sys
... input = repr(sys.stdin.read())
... print sys.argv[0][-14:]
... print sys.argv[1:]
... print input
... if __debug__:
... print 'non-optimized'
... sys.ps1 = '---'
... """ % dict(python_exe=nt_quote_arg(sys.executable)))
>>> input, output = os.popen4(nt_quote_arg(os.path.join(sample_directory,
'foo.exe')))
>>> input.close()
>>> print output.read(),
\foo-script.py
[]
''
---
Testing the GUI Version
-----------------------
Now let's test the GUI version with the simple scipt, bar-script.py:
>>> import os, sys, tempfile
>>> from setuptools.command.easy_install import nt_quote_arg
>>> sample_directory = tempfile.mkdtemp()
>>> open(os.path.join(sample_directory, 'bar-script.pyw'), 'w').write(
... """#!%(python_exe)s
... import sys
... open(sys.argv[1], 'wb').write(repr(sys.argv[2]))
... """ % dict(python_exe=nt_quote_arg(sys.executable)))
We'll also copy gui.exe to the sample-directory with the name bar.exe:
>>> import pkg_resources
>>> open(os.path.join(sample_directory, 'bar.exe'), 'wb').write(
... pkg_resources.resource_string('setuptools', 'gui.exe')
... )
Finally, we'll run the script and check the result:
>>> import os
>>> input, output =
os.popen4('"'+nt_quote_arg(os.path.join(sample_directory, 'bar.exe'))
... + r' "%s" "Test Argument"' %
os.path.join(sample_directory, 'test_output.txt'))
>>> input.close()
>>> print output.read()
<BLANKLINE>
>>> print open(os.path.join(sample_directory, 'test_output.txt'),
'rb').read()
'Test Argument'
We're done with the sample_directory:
>>> import shutil
>>> shutil.rmtree(sample_directory)
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
