Yes, my schools definitely value stability. In fact, I tell the students that if they encounter a bug when running a program, they can be assured that the bug is in their code and not in Python or IDLE (version 2.7).
Irv On Nov 5, 2016, at 7:34 PM, Terry Reedy <tjre...@udel.edu> wrote: > On 11/5/2016 7:19 PM, Irv Kalb wrote: >> This is all great feedback! >> >> My bugs.python.org userid is: IrvKalb >> >> As I am new to the world of IDLE development, do changes you are >> making (or considering), also make it into a release for Python >> 2.7.x? > > While there is greater latitude for backporting IDLE changes than for the > rest of the stdlib, I have pretty much stopped patching 2.7. I posted why > last January (but have made a few changes since). 1. 2.7 is used by people > who want stability, not change. 2. It is too hard to adequately test. A > year ago I introduced bug into 2.7 as a result. A new third reason is that > with 3.6, I can and have started using the ttk widgets introduced a decade > ago. When I redo the debugger window, I will switch it to ttk, as I already > have done, am doing, or will do with everything else. > > > My schools still install 2.7 for use in all of our classes. > > Then they must want stability over enhancement ;-). > > -- > Terry Jan Reedy > > _______________________________________________ > IDLE-dev mailing list > IDLE-dev@python.org > https://mail.python.org/mailman/listinfo/idle-dev > _______________________________________________ IDLE-dev mailing list IDLE-dev@python.org https://mail.python.org/mailman/listinfo/idle-dev
