Re: [Tkinter-discuss] implementation change to simplify Tkinter event loop and threading issues

2018-06-09 Thread engelbert gruber
a PEP of course On 9 June 2018 at 09:31, engelbert gruber wrote: > does this mean there will be a TIP and a GO ? > > On 7 June 2018 at 01:06, Cameron Laird wrote: > >> On Wed, Jun 06, 2018 at 12:55:25PM -0700, Tim Jones wrote: >> . >> . >>

Re: [Tkinter-discuss] implementation change to simplify Tkinter event loop and threading issues

2018-06-09 Thread engelbert gruber
does this mean there will be a TIP and a GO ? On 7 June 2018 at 01:06, Cameron Laird wrote: > On Wed, Jun 06, 2018 at 12:55:25PM -0700, Tim Jones wrote: > . > . > . > > > On Jun 6, 2018, at 11:56 AM, Mark Roseman > wrote:

Re: [Tkinter-discuss] implementation change to simplify Tkinter event loop and threading issues

2018-06-06 Thread Cameron Laird
On Wed, Jun 06, 2018 at 12:55:25PM -0700, Tim Jones wrote: . . . > > On Jun 6, 2018, at 11:56 AM, Mark Roseman wrote: > > > > The best part of this, at least as far as stability goes, is that Tcl > > controls the timing of

Re: [Tkinter-discuss] implementation change to simplify Tkinter event loop and threading issues

2018-06-06 Thread Tim Jones
> On Jun 6, 2018, at 11:56 AM, Mark Roseman wrote: > > The best part of this, at least as far as stability goes, is that Tcl > controls the timing of the calls into Tkinter, so that it will only make them > when it’s “safe” to do so, from a thread it expects to do so from, etc. Given > that