On 10/26/2015 1:15 AM, Terry Reedy wrote:
On 10/22/2015 12:25 PM, Mark Roseman wrote:
A few incremental issues still to be reviewed/integrated:

Since pushing 12+ patches for 10 issues in 2 weeks (September/October), I have focused on Python/IDLE startup problems. The changes for Windows in 3.5.0 introduced some new ones, some of which affect IDLE. For instance, when IDLE starts from the icon, the usual case, it starts in /Windows/system32 instead of the install directory. Two or three people reported problems with this. These multiple unanticipated new problems have made me a bit more cautious. Making IDLE pretty is not much good if people cannot run it.

24455 (fix-mainloop2.patch) fix debugger crash caused by nested main
loops
25313 (missingtheme.patch) isolate code to default to ‘idle classic’ on
missing theme in one place

I am nearly done with my alternative patch. That is about next on my agenda.

24750 (mainwin3.patch) correct visual inconsistencies in editor window
(most jarring and noticeable on mac

As my last message regarding integration plans for the broader changes
(ttk integration, various redesigns, etc.) landed with a resounding
thud,

idledev has mostly been quiet (dead) since I started reading it, early 2013. Last August was the liveliest month I have seen, not at all normal. I still intend to comment on your recent posts.

Can we begin to start checking in these changes into a non-shipping
branch (e.g. 3.6), and when those changes reach a “good enough feature
complete” point they are ported en masse to shipping branch(es)?

I want to continue with incremental patches for now. Undertested re-writes tend to have unanticipated problems.

As a reminder, a running snapshot with these improvements can be found
at https://github.com/roseman/idle

I will look at at least one of those tomorrow (later today, actually).

I instead wrote and pushed a patch inspired by a beginner who posted on python-list. I also researched and opened https://bugs.python.org/issue25488 about sys.path and possible buggy behavior.

--
Terry Jan Reedy


_______________________________________________
IDLE-dev mailing list
IDLE-dev@python.org
https://mail.python.org/mailman/listinfo/idle-dev

Reply via email to