Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
S
setuptools
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jérome Perrin
setuptools
Commits
a75c16ed
Commit
a75c16ed
authored
Jan 01, 2015
by
Jason R. Coombs
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Ported window wrapper tests from doctest to unit tests.
parent
06b3378a
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
178 additions
and
154 deletions
+178
-154
setuptools/tests/test_windows_wrappers.py
setuptools/tests/test_windows_wrappers.py
+178
-0
setuptools/tests/win_script_wrapper.txt
setuptools/tests/win_script_wrapper.txt
+0
-154
No files found.
setuptools/tests/test_windows_wrappers.py
0 → 100644
View file @
a75c16ed
"""
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 graphical programs,
gui.exe. These programs are almost identical, function pretty much
the same way, and are generated from the same source file. 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.
"""
import
os
,
sys
import
textwrap
import
subprocess
import
pytest
from
setuptools.command.easy_install
import
nt_quote_arg
import
pkg_resources
pytestmark
=
pytest
.
mark
.
skipif
(
sys
.
platform
!=
'win32'
,
reason
=
"Windows only"
)
class
WrapperTester
:
@
classmethod
def
create_script
(
cls
,
tempdir
):
"""
Create a simple script, foo-script.py
Note that the script starts with a Unix-style '#!' line saying which
Python executable to run. The wrapper will use this line to find the
correct Python executable.
"""
sample_directory
=
tempdir
script
=
cls
.
script_tmpl
%
dict
(
python_exe
=
nt_quote_arg
(
sys
.
executable
))
f
=
open
(
os
.
path
.
join
(
sample_directory
,
cls
.
script_name
),
'w'
)
f
.
write
(
script
)
f
.
close
()
# also copy cli.exe to the sample directory
f
=
open
(
os
.
path
.
join
(
sample_directory
,
cls
.
wrapper_name
),
'wb'
)
f
.
write
(
pkg_resources
.
resource_string
(
'setuptools'
,
cls
.
wrapper_source
)
)
f
.
close
()
class
TestCLI
(
WrapperTester
):
script_name
=
'foo-script.py'
wrapper_source
=
'cli-32.exe'
wrapper_name
=
'foo.exe'
script_tmpl
=
textwrap
.
dedent
(
"""
#!%(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')
"""
).
lstrip
()
def
test_basic
(
self
,
tmpdir
):
"""
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' suffix 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:
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 need to be escaped
by preceding each of them with back slashes.
"""
sample_directory
=
str
(
tmpdir
)
self
.
create_script
(
sample_directory
)
cmd
=
[
os
.
path
.
join
(
sample_directory
,
'foo.exe'
),
'arg1'
,
'arg 2'
,
'arg "2
\
\
"'
,
'arg 4
\
\
'
,
'arg5 a
\
\
\
\
b'
]
proc
=
subprocess
.
Popen
(
cmd
,
stdout
=
subprocess
.
PIPE
,
stdin
=
subprocess
.
PIPE
)
stdout
,
stderr
=
proc
.
communicate
(
'hello
\
n
world
\
n
'
.
encode
(
'ascii'
))
actual
=
stdout
.
decode
(
'ascii'
).
replace
(
'
\
r
\
n
'
,
'
\
n
'
)
expected
=
textwrap
.
dedent
(
r"""
\foo-script.py
['arg1', 'arg 2', 'arg "2\\"', 'arg 4\\', 'arg5 a\\\\b']
'hello\nworld\n'
non-optimized
"""
).
lstrip
()
assert
actual
==
expected
def
test_with_options
(
self
,
tmpdir
):
"""
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:
"""
sample_directory
=
str
(
tmpdir
)
self
.
create_script
(
sample_directory
)
f
=
open
(
os
.
path
.
join
(
sample_directory
,
'foo-script.py'
),
'w'
)
f
.
write
(
textwrap
.
dedent
(
"""
#!%(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 = '---'
"""
).
lstrip
()
%
dict
(
python_exe
=
nt_quote_arg
(
sys
.
executable
)))
f
.
close
()
cmd
=
[
os
.
path
.
join
(
sample_directory
,
'foo.exe'
)]
proc
=
subprocess
.
Popen
(
cmd
,
stdout
=
subprocess
.
PIPE
,
stdin
=
subprocess
.
PIPE
,
stderr
=
subprocess
.
STDOUT
)
stdout
,
stderr
=
proc
.
communicate
()
actual
=
stdout
.
decode
(
'ascii'
).
replace
(
'
\
r
\
n
'
,
'
\
n
'
)
expected
=
textwrap
.
dedent
(
r"""
\foo-script.py
[]
''
---
"""
).
lstrip
()
assert
actual
==
expected
class
TestGUI
(
WrapperTester
):
"""
Testing the GUI Version
-----------------------
"""
script_name
=
'bar-script.pyw'
wrapper_source
=
'gui-32.exe'
wrapper_name
=
'bar.exe'
script_tmpl
=
textwrap
.
dedent
(
"""
#!%(python_exe)s
import sys
f = open(sys.argv[1], 'wb')
bytes_written = f.write(repr(sys.argv[2]).encode('utf-8'))
f.close()
"""
).
strip
()
def
test_basic
(
self
,
tmpdir
):
"""Test the GUI version with the simple scipt, bar-script.py"""
sample_directory
=
str
(
tmpdir
)
self
.
create_script
(
sample_directory
)
cmd
=
[
os
.
path
.
join
(
sample_directory
,
'bar.exe'
),
os
.
path
.
join
(
sample_directory
,
'test_output.txt'
),
'Test Argument'
,
]
proc
=
subprocess
.
Popen
(
cmd
,
stdout
=
subprocess
.
PIPE
,
stdin
=
subprocess
.
PIPE
,
stderr
=
subprocess
.
STDOUT
)
stdout
,
stderr
=
proc
.
communicate
()
assert
not
stdout
assert
not
stderr
f_out
=
open
(
os
.
path
.
join
(
sample_directory
,
'test_output.txt'
),
'rb'
)
assert
f_out
.
read
().
decode
(
'ascii'
)
==
repr
(
'Test Argument'
)
f_out
.
close
()
setuptools/tests/win_script_wrapper.txt
deleted
100644 → 0
View file @
06b3378a
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 graphical programs,
gui.exe. These programs are almost identical, function pretty much
the same way, and are generated from the same source file. 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()
>>> f = open(os.path.join(sample_directory, 'foo-script.py'), 'w')
>>> bytes_written = f.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)))
>>> f.close()
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
>>> f = open(os.path.join(sample_directory, 'foo.exe'), 'wb')
>>> bytes_written = f.write(
... pkg_resources.resource_string('setuptools', 'cli-32.exe')
... )
>>> f.close()
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' suffix 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 subprocess
>>> cmd = [os.path.join(sample_directory, 'foo.exe'), 'arg1', 'arg 2',
... 'arg "2\\"', 'arg 4\\', 'arg5 a\\\\b']
>>> proc = subprocess.Popen(cmd, stdout=subprocess.PIPE, stdin=subprocess.PIPE)
>>> stdout, stderr = proc.communicate('hello\nworld\n'.encode('ascii'))
>>> bytes = sys.stdout.write(stdout.decode('ascii').replace('\r\n', '\n'))
\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 need to be escaped
by preceding each of 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:
>>> f = open(os.path.join(sample_directory, 'foo-script.py'), 'w')
>>> bytes_written = f.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)))
>>> f.close()
>>> cmd = [os.path.join(sample_directory, 'foo.exe')]
>>> proc = subprocess.Popen(cmd, stdout=subprocess.PIPE, stdin=subprocess.PIPE, stderr=subprocess.STDOUT)
>>> stdout, stderr = proc.communicate()
>>> bytes = sys.stdout.write(stdout.decode('ascii').replace('\r\n', '\n'))
\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()
>>> f = open(os.path.join(sample_directory, 'bar-script.pyw'), 'w')
>>> bytes_written = f.write(
... """#!%(python_exe)s
... import sys
... f = open(sys.argv[1], 'wb')
... bytes_written = f.write(repr(sys.argv[2]).encode('utf-8'))
... f.close()
... """ % dict(python_exe=nt_quote_arg(sys.executable)))
>>> f.close()
We'll also copy gui.exe to the sample-directory with the name bar.exe:
>>> import pkg_resources
>>> f = open(os.path.join(sample_directory, 'bar.exe'), 'wb')
>>> bytes_written = f.write(
... pkg_resources.resource_string('setuptools', 'gui-32.exe')
... )
>>> f.close()
Finally, we'll run the script and check the result:
>>> cmd = [
... os.path.join(sample_directory, 'bar.exe'),
... os.path.join(sample_directory, 'test_output.txt'),
... 'Test Argument',
... ]
>>> proc = subprocess.Popen(cmd, stdout=subprocess.PIPE, stdin=subprocess.PIPE, stderr=subprocess.STDOUT)
>>> stdout, stderr = proc.communicate()
>>> print(stdout.decode('ascii'))
<BLANKLINE>
>>> f_out = open(os.path.join(sample_directory, 'test_output.txt'), 'rb')
>>> print(f_out.read().decode('ascii'))
'Test Argument'
>>> f_out.close()
We're done with the sample_directory:
>>> import shutil
>>> shutil.rmtree(sample_directory)
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment