Talking of updates to IDLE

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Talking of updates to IDLE

phil jones-5
Did the VIDLE changes and fixes ever get back into normal IDLE?


phil
_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev
Reply | Threaded
Open this post in threaded view
|

Re: Talking of updates to IDLE

Bruce Sherwood
As far as I know, no. It's a good example of the very slow pace of
making changes. The VIDLE work was completed by Guilherme Polo in the
2009 Google Summer of Code, in a Python-community sanctioned project,
and Guido has given his blessing to the changes, but the process for
getting changes into the standard IDLE distribution remains opaque and
glacial. I gather it isn't anyone's "fault", and people are busy, but
somehow IDLE is an orphan in comparison with other aspects of Python.

Bruce Sherwood

On Tue, Apr 12, 2011 at 5:59 PM, phil jones <[hidden email]> wrote:
> Did the VIDLE changes and fixes ever get back into normal IDLE?
>
>
> phil
> _______________________________________________
> IDLE-dev mailing list
> [hidden email]
> http://mail.python.org/mailman/listinfo/idle-dev
>
_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev
Reply | Threaded
Open this post in threaded view
|

Re: Talking of updates to IDLE

Tal Einat
In reply to this post by phil jones-5
Unfortunately, no.

I volunteered to do so about six months ago, but ended up not be able to free the time required.

If anyone else wants to do this, go ahead, I haven't even made any significant progress :(

On Wed, Apr 13, 2011 at 2:59 AM, phil jones <[hidden email]> wrote:
Did the VIDLE changes and fixes ever get back into normal IDLE?


phil
_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev


_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev
Reply | Threaded
Open this post in threaded view
|

Re: Talking of updates to IDLE

Ned Deily
In reply to this post by Bruce Sherwood
In article <[hidden email]>,
 Bruce Sherwood <[hidden email]> wrote:
> As far as I know, no. It's a good example of the very slow pace of
> making changes. The VIDLE work was completed by Guilherme Polo in the
> 2009 Google Summer of Code, in a Python-community sanctioned project,
> and Guido has given his blessing to the changes, but the process for
> getting changes into the standard IDLE distribution remains opaque and
> glacial. I gather it isn't anyone's "fault", and people are busy, but
> somehow IDLE is an orphan in comparison with other aspects of Python.

It's not so much opaque as it is time-consuming and a fair amount of
work.  I promised to review them and get them in and I'm still intending
to do that.  I'm sorry it's taking this long.  For one thing, getting
the 3.2 release out the door turned got in the way.  The fixes
themselves need work to be upgraded to the latest releases and then
there is testing that needs to be done on all platforms.  If anyone is
willing to help out with the testing, especially experienced Windows
users of IDLE, it would be a great to have your help when ready.

--
 Ned Deily,
 [hidden email]

_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev
Reply | Threaded
Open this post in threaded view
|

Re: Talking of updates to IDLE

Tal Einat
I would be willing to help with testing, and have quite some experience with testing IDLE.

On Wed, Apr 13, 2011 at 4:20 AM, Ned Deily <[hidden email]> wrote:
In article <[hidden email]>,
 Bruce Sherwood <[hidden email]> wrote:
> As far as I know, no. It's a good example of the very slow pace of
> making changes. The VIDLE work was completed by Guilherme Polo in the
> 2009 Google Summer of Code, in a Python-community sanctioned project,
> and Guido has given his blessing to the changes, but the process for
> getting changes into the standard IDLE distribution remains opaque and
> glacial. I gather it isn't anyone's "fault", and people are busy, but
> somehow IDLE is an orphan in comparison with other aspects of Python.

It's not so much opaque as it is time-consuming and a fair amount of
work.  I promised to review them and get them in and I'm still intending
to do that.  I'm sorry it's taking this long.  For one thing, getting
the 3.2 release out the door turned got in the way.  The fixes
themselves need work to be upgraded to the latest releases and then
there is testing that needs to be done on all platforms.  If anyone is
willing to help out with the testing, especially experienced Windows
users of IDLE, it would be a great to have your help when ready.

--
 Ned Deily,
 [hidden email]

_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev


_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev
Reply | Threaded
Open this post in threaded view
|

Re: Talking of updates to IDLE

phelix
> If anyone is
> willing to help out with the testing, especially experienced Windows
> users of IDLE, it would be a great to have your help when ready.
windows user, willing to test
Reply | Threaded
Open this post in threaded view
|

Re: Talking of updates to IDLE

phil jones-5
I'd be willing to help with testing of IDLE on Ubuntu if there's a
need for that. Is there a document (say a wiki page somewhere) which
tells us what / how to test?

phil

On Wed, Apr 13, 2011 at 8:24 AM, phelix <[hidden email]> wrote:

>
>> If anyone is
>> willing to help out with the testing, especially experienced Windows
>> users of IDLE, it would be a great to have your help when ready.
> windows user, willing to test
> --
> View this message in context: http://old.nabble.com/Talking-of-updates-to-IDLE-tp31383770p31385488.html
> Sent from the Python - idle-dev mailing list archive at Nabble.com.
>
> _______________________________________________
> IDLE-dev mailing list
> [hidden email]
> http://mail.python.org/mailman/listinfo/idle-dev
>
_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev
Reply | Threaded
Open this post in threaded view
|

Re: Talking of updates to IDLE

Ned Deily
In article <BANLkTimd8hjpTUgusUS=[hidden email]>,
 phil jones <[hidden email]> wrote:
> I'd be willing to help with testing of IDLE on Ubuntu if there's a
> need for that. Is there a document (say a wiki page somewhere) which
> tells us what / how to test?

Not that I'm aware of.  Perhaps someone else knows of something? Writing
some test session recipes would be a good start towards repeatable and
possibly more automated testing.

And thanks all for the testing offers.

--
 Ned Deily,
 [hidden email]

_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev
Reply | Threaded
Open this post in threaded view
|

Re: Talking of updates to IDLE

Tal Einat
The problem is that what one should test depends highly on what changes have been made. This is true always in the absence of a test suite, I guess. My point is that I can think of quite a few "testing recipes" but their coverage would be rather low, so I'm not sure how useful they would be.

Also, the ability to write tests when fixing bugs which make sure the bugs stay fixed is IMO a basic requirement. Doing this with recipes would make quickly make testing too time consuming.

Perhaps tests written with something like Sikuli?

- Tal

On Thu, Apr 14, 2011 at 1:36 AM, Ned Deily <[hidden email]> wrote:
In article <BANLkTimd8hjpTUgusUS=[hidden email]>,
 phil jones <[hidden email]> wrote:
> I'd be willing to help with testing of IDLE on Ubuntu if there's a
> need for that. Is there a document (say a wiki page somewhere) which
> tells us what / how to test?

Not that I'm aware of.  Perhaps someone else knows of something? Writing
some test session recipes would be a good start towards repeatable and
possibly more automated testing.

And thanks all for the testing offers.

--
 Ned Deily,
 [hidden email]

_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev


_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev
Reply | Threaded
Open this post in threaded view
|

Re: Talking of updates to IDLE

Terry Reedy
On 4/14/2011 7:32 PM, Tal Einat wrote:

> Perhaps tests written with something like Sikuli <http://sikuli.org/>?

I have thought of that too. I just found this page:
http://sikuli.org/docx/faq/020-unit-test.html

--
Terry Jan Reedy

_______________________________________________
IDLE-dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/idle-dev