Re: [Idle-dev] Fixing and Improving IDLE

2011-12-20 Thread phil jones
On the subject of forking and remerging etc. where's the IDLE code? Would it be a good idea to move it to GitHub or BitBucket under git or hg? Also, I'd suggest that if there's a page with information for developers, someone links to it from http://wiki.python.org/moin/IDLE regards phil On Wed

Re: [Idle-dev] Fixing and Improving IDLE

2011-12-20 Thread Roger Serwy
The IDLE code is included with the standard library. It can be found in the Mercurial repository referenced at http://docs.python.org/devguide/ I agree that the wiki should include this information. - Roger On 12/20/2011 06:58 AM, phil jones wrote: On the subject of forking and remerging etc.

Re: [Idle-dev] Fixing and Improving IDLE

2011-12-20 Thread phil jones
Seems a bit of overkill to have to check out the entire developers edition of python. Doesn't hg have submodules? Even if IDLE is in the standard library, it must be possible to treat it as a separate project from the developer's perspective and then merge it in when building a distribution. phil

Re: [Idle-dev] Fixing and Improving IDLE

2011-12-20 Thread Roger Serwy
As far as I know, Mercurial does not support partial checkout. See http://mercurial.selenic.com/bts/issue105 - Roger On 12/20/2011 10:40 AM, phil jones wrote: Seems a bit of overkill to have to check out the entire developers edition of python. Doesn't hg have submodules? Even if IDLE is in t

Re: [Idle-dev] Fixing and Improving IDLE

2011-12-20 Thread Terry Reedy
I have considered the possibility of separating IDLE, but I see two problems. 1. Although the IDLE code is currently very similar for each current Python version, it is not exactly the same. Py2/Py3 differences are obvious. Less obvious is that if we use ttk widgets, such as tabbed windows, a