I've filed http://bugs.python.org/issue18882 for this.
On Fri, Aug 30, 2013 at 12:52 PM, Andrew Svetlov <[email protected]> wrote: > _MainThread can be used as workaround, but adding public function makes value. > > Oleg, as I understand _MainThread is a class, not class instance, test > for threading._MainThread.ident doesn't make sense. > > On Fri, Aug 30, 2013 at 12:44 PM, Oleg Broytman <[email protected]> wrote: >> On Fri, Aug 30, 2013 at 12:24:07PM +0300, Andrew Svetlov >> <[email protected]> wrote: >>> Main thread is slightly different from others. >>> Signals can be subscribed from main thread only. >>> Tulip has special logic for main thread. >>> In application code we can explicitly know which thread is executed, >>> main or not. >>> But from library it's not easy. >>> Tulip uses check like >>> threading.current_thread().name == 'MainThread' >>> This approach has a problem: thread name is writable attribute and can >>> be changed by user code. >> >> You can test >> threading.current_thread().__class__ is threading._MainThread >> or >> threading.current_thread().ident == threading._MainThread.ident >> >>> My proposition is to add function like get_mainthread_id() -> int >>> which return ident for main thread >> >> threading._MainThread.ident ? >> >> Oleg. >> -- >> Oleg Broytman http://phdru.name/ [email protected] >> Programmers don't die, they just GOSUB without RETURN. >> _______________________________________________ >> Python-Dev mailing list >> [email protected] >> http://mail.python.org/mailman/listinfo/python-dev >> Unsubscribe: >> http://mail.python.org/mailman/options/python-dev/andrew.svetlov%40gmail.com > > > > -- > Thanks, > Andrew Svetlov -- Thanks, Andrew Svetlov _______________________________________________ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
