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:
>> .
>> .
>>
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:
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
> 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
I’m not sure if this is the right place to discuss internal implementation
details, so apologies in advance if not…
Ivan and I have been going back and forth regarding some of the subtleties of
how Tkinter and Tcl/Tk interact, which can come up particularly with regards to
threads, but also in