On Tue, Feb 19, 2013 at 09:48:16PM -0500, Todd Rovito wrote:
-Does it make sense to separate IDLE from the stdlib for Python 3.4? I understand the batteries included argument, but if IDLE development is going to continue to proceed at a more accelerated pace than Python, it might make sense to separate it out into its own project or a sub-project.
Personally, I don't use IDLE, but I know many people who do. I think it is important for them that IDLE remains in the std lib. We could have a stable version of IDLE in the std lib, and another version available on PyPI. The PyPI version could change more rapidly, since it doesn't have to fit in with the release schedule for the std lib. As the release schedule allows, the two branches could be merged. I have no idea if this has been tried before, but I think this would work better for an application like IDLE than for a library. -- Steven