Lines Matching refs:interpreter

17 Python code, which can be  :ref:`executed directly by the Python interpreter
67 .. cmdoption:: -p <interpreter>, --python=<interpreter>
69    Add a ``#!`` line to the archive specifying *interpreter* as the command
93    Display the interpreter embedded in the archive, for diagnostic purposes.  In
110 .. function:: create_archive(source, target=None, interpreter=None, main=None, filter=None, compres…
120      the target (modifying it to reflect the value given for the *interpreter*
137    The *interpreter* argument specifies the name of the Python
138    interpreter with which the archive will be executed.  It is written as
141    launcher.  Omitting the *interpreter* results in no shebang line being
142    written.  If an interpreter is specified, and the target is a
179    Return the interpreter specified in the ``#!`` line at the start of the
203 To make the application directly executable on POSIX, specify an interpreter
233 .. _zipapp-specifying-the-interpreter:
238 Note that if you specify an interpreter and then distribute your application
239 archive, you need to ensure that the interpreter used is portable.  The Python
293       $ python -m zipapp -p "interpreter" myapp
296 the appropriate interpreter available. See :ref:`zipapp-specifying-the-interpreter`
302 the Python interpreter registers the ``.pyz`` and ``.pyzw`` file extensions
410    conventional Python interpreter.  Your code and its dependencies need to be
414    standard Python interpreter.
429 line to the file (``#!/path/to/interpreter``).
434    interpreter name, and then a newline (``b'\n'``) character.  The interpreter
436    launcher on Windows.  The interpreter should be encoded in UTF-8 on Windows,