2013/3/20 Barry Warsaw <ba...@python.org>: > On Mar 20, 2013, at 11:22 AM, Eli Bendersky wrote: > >>IDLE would be a great first foray into this "separate project" world, >>because it is many ways a separate project. > > I really think that's true. A separate project, occasionally sync'd back into > the stdlib by a core dev seems like the right way to manage IDLE.
I would advise against this. Basically, every "externally-maintained" package with have causes pain. For example, the stdlib now has some long-diverged fork of simplejson. With xml.etree, it was not clear for years whether core developers could touch it even though the external project had died. Either the stdlib and IDLE should go separate ways or development has to happen in the stdlib with CPython release schedule and policies. -- Regards, Benjamin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
