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 r.david.murray
Recipients Arfrever, bra, christian.heimes, flox, jcea, pitrou, r.david.murray
Date 2012-08-06.13:17:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344259037.73.0.380972057463.issue15500@psf.upfronthosting.co.za>
In-reply-to
Content
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 the OS, but I don't think the convenience of that is worth introducing a potential backward incompatibility.

On the other hand, I think this might be an appropriate place to use a global control, so that getting thread names out to the OS would require adding just a single line of code to any given application.  I know of an application that does this.  It chose to implement it as a global change, and that makes sense to me.
History
Date User Action Args
2012-08-06 13:17:17r.david.murraysetrecipients: + r.david.murray, jcea, pitrou, christian.heimes, Arfrever, flox, bra
2012-08-06 13:17:17r.david.murraysetmessageid: <1344259037.73.0.380972057463.issue15500@psf.upfronthosting.co.za>
2012-08-06 13:17:16r.david.murraylinkissue15500 messages
2012-08-06 13:17:16r.david.murraycreate