On Sep 25, 2013, at 7:04 PM, Barry Warsaw <ba...@python.org> wrote: > Another reason to oppose this is what I've heard quite often from people > regarding Python 2.7. I've been told that many folks are actually really > happy with using 2.7 precisely because it extremely stable. They don't have > to worry about their stuff breaking or incompatibilities cropping up, because > it *doesn't* change. Python 2.7 is like a long-term maintenance release, with > guaranteed multi-year stability, and I think while that was unintended, it's a > *good* thing. This PEP proposes to break that, and I'm loathe to give up that > good reputation for this particular feature.
Maybe I'm just naive but can you expand on how adding a module that nothing else in the system imports (besides the installers; but you weren't arguing against adding this to the installers) would break someones use any other module? If they don't import it (which the vast bulk of people won't directly, nor at all during the operation of their applications) how does it's existence on the file system risk a breakage to their system? ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
