[Python-Dev] Accepting PEP 434, Idle Enhancement Exception
Todd Rovito
rovitotv at gmail.com
Sat Mar 30 04:01:09 CET 2013
More information about the Python-Dev mailing list
Sat Mar 30 04:01:09 CET 2013
- Previous message: [Python-Dev] Accepting PEP 434, Idle Enhancement Exception
- Next message: [Python-Dev] Accepting PEP 434, Idle Enhancement Exception
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Mar 29, 2013 at 10:40 PM, Maciej Fijalkowski <fijall at gmail.com>wrote: > Does that mean that mainstream idle development should move out of the > python tree? No the acceptance of PEP-434 does not mean IDLE development should move out of the python tree. The acceptance of PEP-434 means that the restriction on applying enhancements be relaxed for IDLE code residing in ../Lib/idlelib. In other words Python Core Developers can apply enhancements (but not major rewrites) even to the 2.7 branch. The relaxation was requested in the hope that we can apply many of the already existing patches quickly and allow IDLE to become a high quality cross-platform default starting point for new Python users that aren't already accustomed to the command line and editing text files directly. PEP-434 doesn't suggest moving the IDLE code outside of the Python tree. Please let me know if you have additional questions, feel free to help us with IDLE development! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130329/9624decb/attachment.html>
- Previous message: [Python-Dev] Accepting PEP 434, Idle Enhancement Exception
- Next message: [Python-Dev] Accepting PEP 434, Idle Enhancement Exception
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list