In article <CAP7+vJ+hu8AUzwRWyuV1NuR0r=HzZQUgqHAqyXcGsPi=2sn...@mail.gmail.com>, Guido van Rossum <[email protected]> wrote: > On Tue, Feb 11, 2014 at 2:47 PM, Ned Deily <[email protected]> wrote: > > IDLE is part of the Python standard library and, as such, is developed > > using the same process as other parts of the library, with a few > > variations (primarily as described in PEP 434). The process is > > described in detail in the Python Developer's Guide. [...] > However, some of the complaints about the development process might benefit > from a different approach (presumably after a fork). Or maybe not, that's > the question.
Whether or not it might, understanding and building on the current process and documentation seems like a good first step in any case. -- Ned Deily, [email protected] _______________________________________________ IDLE-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/idle-dev
