![]() Not supported in the virtual shebang line at all. Line nominates simply “python” - in fact, the trailing ‘w’ notation is Will attempt to locate and launch pythonw.exe even if a virtual shebang The “windows” (ie., GUI) version of the launcher The console launcher will be named ‘py.exe’ and the Windows To the ‘python.exe’ and ‘pythonw.exe’ executables which currently ship One which is a “windows” (ie., GUI) program. The launcher comes in 2 versions - one which is a console program and Long as the features prescribed here continue to work. New features may be added to the launcher as Together with the Windows installer of Python, but will also beĪvailable separately (but released along with the Python Implementation is provided in which will be distributed This PEP specifies features of the launcher a prototype Specified without inventing new syntax or conventions to describe This PEP - the primary motivation is to allow a specific version to be ![]() Work on both Windows and Unix, this is not the primary motivation for While this PEP offers the ability to use a shebang line which should Platform and therefore allows the launcher to be the executableĪssociated with ‘.py’ files to support multiple Python versions Launcher which can offer the same benefits for Python on the Windows This PEP describes an implementation of a Predictable way of both starting Python interactively and for allowing These 2 facilities combined allow for a portable and somewhat Referenced in the shebang line or in the PATH.) PEP 394 ‘The “python”Ĭommand on Unix-Like Systems’ describes additional conventionsįor more fine-grained specification of a particular Python version. Requiring the path where Python is actually installed to be Where Python it actually installed on the machine (eg., without These symbolic links allow Python to be executed without regard for Particular version of Python installed under the operating-system. Systems will have a link /usr/bin/python which references a Python executables in well-known directories. This is described inĭetail in the evecve(2) man page and while user documentation willīe created for this feature, for the purposes of this PEP that manĪdditionally, these operating systems provide symbolic-links to PEP) allow scripts to be executed as if they were executable imagesīy examining the script for a “shebang” line which specifies theĪctual executable to be used to run the script. Unix-like operating systems (referred to simply as “Unix” in this To nominate the version of Python they need by way of a “shebang” line, as ![]() ![]() The existing practices of another operating system - scripts will be able On the Python version the script targets. To allow files with a ‘.py’ extension to use a different executable based Incompatible with Python 2.x scripts, a different strategy must be used As Python 3.x scripts are often syntactically Ideal, has generally been workable due to the conservative changes in With an extension, allowing for scripts to be executed directly in someĬontexts (eg., double-clicking the file in Windows Explorer.) Until now,Ī strategy of “last installed Python wins” has been used and while not Windows provides “file associations” so an executable can be associated Heuristics to locate a Python executable and launch it with a Python launcher is a single executable which uses a number of This PEP describes a Python launcher for the Windows platform. ![]() Löwis Status : Final Type : Standards Track Created : 1 Python-Version : 3.3 Post-History : 2, 1, 1 Resolution : Python-Dev message Toggle light / dark / auto colour theme PEP 397 – Python launcher for Windows Author : Mark Hammond , PEP 397 – Python launcher for Windows | Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |