Message410896
| Author |
arhadthedev |
| Recipients |
Arfrever, ZackerySpytz, arhadthedev, asvetlov, bra, christian.heimes, eryksun, flox, jcea, kovid, pitrou, r.david.murray, socketpair, vstinner |
| Date |
2022年01月18日.21:26:34 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1642541194.88.0.319397182535.issue15500@roundup.psfhosted.org> |
| In-reply-to |
| Content |
@r.david.murray
> 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.
For now, Python thread names are always empty (as in many other programs). So Python-oriented tools that could expect some other outcome to bother check the names are just impossible (there is no alternative semantics they could perform in non-empty case). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2022年01月18日 21:26:34 | arhadthedev | set | recipients:
+ arhadthedev, jcea, pitrou, vstinner, christian.heimes, Arfrever, r.david.murray, asvetlov, flox, bra, kovid, socketpair, eryksun, ZackerySpytz |
| 2022年01月18日 21:26:34 | arhadthedev | set | messageid: <1642541194.88.0.319397182535.issue15500@roundup.psfhosted.org> |
| 2022年01月18日 21:26:34 | arhadthedev | link | issue15500 messages |
| 2022年01月18日 21:26:34 | arhadthedev | create |
|