Message315285
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | Ivan.Pozdeev |
|---|---|
| Recipients | Ivan.Pozdeev, serhiy.storchaka, terry.reedy |
| Date | 2018-04-14.08:56:25 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1523696186.2.0.682650639539.issue33257@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
@terry.reedy Apparently, this bug has gone unnoticed for years (to be precise, since https://github.com/python/cpython/commit/b5bfb9f38c786c3330b2d52d93b664588c42283d in 2002), and there are all kinds of weird rumors circulating about whether tkinter is thread-safe or not, and what can be run where ( see e.g. https://stackoverflow.com/search?q=tkinter+thread+safe ). Having run into it in my project, I set out to get to the bottom of this ( https://github.com/RedFantom/mtTkinter/issues/5 ) ...and looks like I did. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-04-14 08:56:26 | Ivan.Pozdeev | set | recipients: + Ivan.Pozdeev, terry.reedy, serhiy.storchaka |
| 2018-04-14 08:56:26 | Ivan.Pozdeev | set | messageid: <1523696186.2.0.682650639539.issue33257@psf.upfronthosting.co.za> |
| 2018-04-14 08:56:26 | Ivan.Pozdeev | link | issue33257 messages |
| 2018-04-14 08:56:25 | Ivan.Pozdeev | create | |