I'd like to put a stop to all changes to the version of IDLE in the Python source tree (Tools/idle/* -- let's call it Python-idle). The current crop of changes are being merged into Idlefork, the separate SF project where a new IDLE version is being cooked. I hope that Idlefork will be ready to be merged back into Python before we release Python 2.3, and that will be easiest if we can simply abandon the existing Python-idle code and copy the latest Idlefork in its place. Any changes made to the Python-idle code will be lost at that point. If you have a bug, fix or feature for IDLE, please suggest it on the idle-dev mailing list or on Idlefork's SF bug/patch managers! --Guido van Rossum (home page: http://www.python.org/~guido/)
Guido van Rossum <guido@python.org> writes:
I'd like to put a stop to all changes to the version of IDLE in the Python source tree (Tools/idle/* -- let's call it Python-idle). The current crop of changes are being merged into Idlefork, the separate SF project where a new IDLE version is being cooked.
Does Idlefork also require CVS Python? Regards, Martin
I'd like to put a stop to all changes to the version of IDLE in the Python source tree (Tools/idle/* -- let's call it Python-idle). The current crop of changes are being merged into Idlefork, the separate SF project where a new IDLE version is being cooked.
Does Idlefork also require CVS Python?
Not yet, AFAIK, it requires 2.2. A very small number of changes to Python-idle could not be merged for that reason (e.g. mkstemp). I'd like to keep Idlefork working with 2.2 so there's a reasonable potential user base for an Idlefork release. --Guido van Rossum (home page: http://www.python.org/~guido/)
participants (2)
-
Guido van Rossum -
martin＠v.loewis.de