[Python-Dev] Integrating the PEP 397 launcher (original) (raw)
martin at v.loewis.de martin at v.loewis.de
Fri Mar 30 05:48:42 CEST 2012
- Previous message: [Python-Dev] Integrating the PEP 397 launcher
- Next message: [Python-Dev] Integrating the PEP 397 launcher
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Zitat von Brian Curtin <brian at python.org>:
After talking with Martin and several others during the language summit and elsewhere around PyCon, PEP 397 should be accepted. I don't remember who, but some suggested it should just be a regular old feature instead of going through the PEP process. So...does this even need to continue the PEP process?
I don't think PEP 397 can be accepted as it stands; it has too many open issues. However, I am in favor of accepting the proposed feature.
Now that we do have the PEP, I think that should be done properly. I thought you offered to rewrite it. Formally, I could accept the PEP being withdrawn, and the feature integrated anyway, but I still consider that bad style.
So: I can offer to rewrite the PEP to give a full specification of the feature. It might be that I still need some help to provide end-user prose in the PEP if people would want to see that as well.
Regards, Martin
- Previous message: [Python-Dev] Integrating the PEP 397 launcher
- Next message: [Python-Dev] Integrating the PEP 397 launcher
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]