Neil Hodgson nyamatongwe at gmail.com
Wed Aug 5 11:09:10 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:

> Or don't you understand why that single unresolved item didn't manage
> to revert the decision? Well, there are many unresolved items in
> the Mercurial conversion, some much more stressful than the eol issue
> (e.g. the branching discussion).

   Then these issues should have been included in the initial PEP for
choosing a DVCS since the issues could have driven the choice. PEP 374
implies that win32text effectively solves the Windows eol issue which
no longer appears to be correct.

   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 ]

---

More information about the Python-Dev mailing list