[Idle-dev] Suggestions idle-dev

[Bruce Sherwood]

I'm associated with VIDLE and I read this list. VIDLE was created by
David Scherer and Guilherme Polo, neither of whom is now an active
developer. I worked with them but over the years have not contributed
much to this myself. I did however make a version that runs on Python
3. I'm the main developer of VPython (an easy to use 3D programming
environment, see vpython.org) and I bundle VIDLE with the Windows and
Mac installers for VPython, and offer a VIDLE package for Linux.

My own strong interest in IDLE springs from being co-author of an
intro physics curriculum (matterandinteractions.org) within which
thousands of college engineering and science students each semester
write Python programs, using the VPython module, to model physical
systems in 3D. Because few of these students have ever written a line
of code before coming to the physics course, IDLE is vitally important
as a lightweight, easy to use IDE.

Bruce

On Wed, Apr 13, 2011 at 3:56 AM, phil jones <interstar at gmail.com> wrote:
> I can't help noticing that IDLE has a history of people forking it in
> order to get development work done faster (ie. Idlefork, VIDLE etc.)
>
> So it seems that to ramp up progress we may need our own space. (Eg.a
> wiki, a mercurial (or git) code repository, a bug tracker).
>
> Ideally, perhaps there could be a continuity with those other projects
> - are the people behind Idlefork and VIDLE reading this list? I know
> that those projects had specific goals, but I wonder whether there
> isn't a role for a standard Idle-fork project kept somewhere like
> Github or Butbucket which everyone who's interested in further
> development of Idle could work against.
>
> I know there'd still be an issue of getting this back into the main
> Python tree, but if it took off (and IDLE development was seen to have
> more direction and be moving faster) then there'd be more of an
> incentive for the rest of the Python development community to support
> that too.
>
> phil
>
>>
>> I would like to make my suggestions more concrete:
>> * easy access to idle-dev and/or description on the IDLE homepage
>> * a wiki for IDLE development
>> * a wiki for using IDLE
>> * a bug-tracker aside from Python bug-tracker
>> * a feature-tracker
>> * all this accessible from the homepage
>> * an invitation to contribute on the IDLE startup console or at least the
>> about window and installer
>>
>> =Phelix=
> _______________________________________________
> IDLE-dev mailing list
> IDLE-dev at python.org
> http://mail.python.org/mailman/listinfo/idle-dev
>