[issue15500] Python should support naming threads

Changes by Марк Коренберг : -- nosy: +mmarkk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue15500] Python should support naming threads

Kovid Goyal added the comment: Just FYI, a pure python2 implementation that monkey patches Thread.start() to set the OS level thread name intelligently. import ctypes, ctypes.util, threading libpthread_path = ctypes.util.find_library("pthread") if libpthread_path:

[issue15500] Python should support naming threads

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue15500] Python should support naming threads

R. David Murray added the comment: It is indeed the compatibility that is the worse issue. The problem is what people have gotten used to and may have coded their applications to expect/deal with. I agree with you that most people would *not* find it surprising to see the name reflected in t

[issue15500] Python should support naming threads

Changes by R. David Murray : -- Removed message: http://bugs.python.org/msg167559 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue15500] Python should support naming threads

R. David Murray added the comment: It is indeed the compatibility that is the worse issue. The problem is what people have gotten used to and may have coded their applications to expect/deal with. what people have gotten used to. I agree with you that most people would *not* find it surprisi

[issue15500] Python should support naming threads

Attila Nagy added the comment: "I don't think this should be done by default as it will break people's expectations and, perhaps worse, compatibility." I won't mind another thread naming API, if somebody does this. :) But personally I expected python to name my threads (and if the OS supports it

[issue15500] Python should support naming threads

Antoine Pitrou added the comment: I don't think this should be done by default as it will break people's expectations and, perhaps worse, compatibility. -- nosy: +pitrou ___ Python tracker

[issue15500] Python should support naming threads

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue15500] Python should support naming threads

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue15500] Python should support naming threads

Christian Heimes added the comment: +1 win32 supports thread names, too. http://msdn.microsoft.com/en-us/library/xcb2z8hs.aspx -- nosy: +christian.heimes ___ Python tracker ___

[issue15500] Python should support naming threads

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue15500] Python should support naming threads

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15500] Python should support naming threads

Changes by Antoine Pitrou : -- versions: +Python 3.4 -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15500] Python should support naming threads

New submission from Attila Nagy: Python class Thread has a "name" argument, which sets the name of the given thread. This name is used only internally, while there is a possibility to set this on an OS-level. Related discussion: http://stackoverflow.com/questions/2369738/can-i-set-the-name-of-a