[Python-Dev] PEP 385: the eol-type issue (original) (raw)
Neil Hodgson nyamatongwe at gmail.com
Wed Aug 5 10:25:08 CEST 2009
- Previous message: [Python-Dev] PEP 385: the eol-type issue
- Next message: [Python-Dev] PEP 385: the eol-type issue
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Martin v. Löwis:
Is it really that you don't understand? It's fairly easy: there was a PEP ...
The PEP process is straightforward. However, a PEP may produce an outcome that proves after more experience to be wrong. ISTM a prerequisite to choosing a DVCS is that it should support the full range of development platforms and thus the PEP was accepted prematurely. At some point the PEP should be reexamined and, if necessary, rescinded. What I don't understand is why the plan is still to move to hg despite, after several months, there not being a known good way to include Windows eol support.
Neil
- Previous message: [Python-Dev] PEP 385: the eol-type issue
- Next message: [Python-Dev] PEP 385: the eol-type issue
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]