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 bra
Recipients Arfrever, bra, christian.heimes, flox, jcea, pitrou, r.david.murray
Date 2012-08-06.10:22:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344248538.86.0.193059564225.issue15500@psf.upfronthosting.co.za>
In-reply-to
Content
"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, on that level), I was actually surprised to see that it doesn't, mostly because I remembered a patch for FreeBSD, which did this years ago, so I thought it has been merged into mainline since then.
History
Date User Action Args
2012-08-06 10:22:18brasetrecipients: + bra, jcea, pitrou, christian.heimes, Arfrever, r.david.murray, flox
2012-08-06 10:22:18brasetmessageid: <1344248538.86.0.193059564225.issue15500@psf.upfronthosting.co.za>
2012-08-06 10:22:18bralinkissue15500 messages
2012-08-06 10:22:18bracreate