[Python-Dev] Status of PEP 397 (original) (raw)

[Python-Dev] Status of PEP 397 - Python launcher for Windows

martin at v.loewis.de martin at v.loewis.de
Sat Feb 18 13:08:21 CET 2012

Zitat von Mark Hammond <skippy.hammond at gmail.com>:

I'm wondering what thoughts are on PEP 397, the Python launcher for Windows. I've been using the implementation for a number of months now and I find it incredibly useful.

I wonder what the rationale for the PEP (as opposed to the rationale for the launcher) is - why do you need to have a PEP for it? As written, it specifies some "guidelines" that some software package of yours might adhere to. You don't need a PEP for that, just write the software and adhere to the guidelines, possibly putting them into the documentation.

A PEP needs to have controversial issues, or else there would not have been a point in writing it in the first place. Also, it needs to concern CPython, or the Python language, else it does not need to be a PEP.

To be a proper PEP, you need to include these things:

Assuming you are proposing some future action for CPython, I'm opposed to the notion that the implementation of the launcher is the specification. The specification needs to be in the PEP. It may leave room, in which case the remaining details need to be specified in the documentation.

A critical question (IMO) is the question how the launcher gets onto systems. Will people have to download and install it themselves, or will it come as part of some Python distribution? If it comes with the Python distribution, how get multiple copies of the launcher coordinated?

Also: what's the name of the launcher? How can I actually use it?

Regards, Martin

More information about the Python-Dev mailing list