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 kommentar(er)
