On 14.05.2018 22:05, Ivan Pozdeev wrote:
On 14.05.2018 21:58, Terry Reedy wrote:
On 5/14/2018 12:20 PM, Chris Barker via Python-Dev wrote:
On Wed, May 2, 2018 at 8:21 PM, Terry Reedy > wrote:
On 5/2/2018 4:38 PM, Ivan Pozdeev via Python-Dev
On 14.05.2018 21:58, Terry Reedy wrote:
On 5/14/2018 12:20 PM, Chris Barker via Python-Dev wrote:
On Wed, May 2, 2018 at 8:21 PM, Terry Reedy > wrote:
On 5/2/2018 4:38 PM, Ivan Pozdeev via Python-Dev wrote:
The bottom line is: Tkinter is
On 5/14/2018 12:20 PM, Chris Barker via Python-Dev wrote:
On Wed, May 2, 2018 at 8:21 PM, Terry Reedy > wrote:
On 5/2/2018 4:38 PM, Ivan Pozdeev via Python-Dev wrote:
The bottom line is: Tkinter is currently broken
This is way
On Wed, May 2, 2018 at 8:21 PM, Terry Reedy wrote:
> On 5/2/2018 4:38 PM, Ivan Pozdeev via Python-Dev wrote:
>
>> The bottom line is: Tkinter is currently broken
>>
>
> This is way over-stated. Many modules have bugs, somethings in features
> more central to their main
On 5/2/2018 4:38 PM, Ivan Pozdeev via Python-Dev wrote:
The bottom line is: Tkinter is currently broken
This is way over-stated. Many modules have bugs, somethings in features
more central to their main purpose.
-- as in, it's not thread-safe (in both Py2 and Py3)
Meaning that tkinter
The bottom line is: Tkinter is currently broken -- as in, it's not
thread-safe (in both Py2 and Py3) despite being designed and advertizing
itself as such.
All the fix options require some redesign of either `_tkinter', or some
of the core as well.
So, I'd like to get some kind of core team's