➜

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.

作者 tim.peters
收信人 asvetlov, eric.snow, ncoghlan, pitrou, tim.peters
日期 2017-09-20.02:28:41
SpamBayes Score -1.0
Marked as misclassified 是
Message-id <1505874521.69.0.295758998992.issue31517@psf.upfronthosting.co.za>
In-reply-to
内容
Is there a problem here?  I haven't heard of anyone even wondering about this before.  threading.py worries about Threads created _by_ threading.py, plus the magical (from its point of view) thread that first imports threading.py.  Users mix in `_thread` threads, or raw C threads from extension modules, essentially at their own risk.  Which risks are minimal, but can have visible consequences.

I don't view that as being a real problem.  It might help if, e.g., a Wiki somewhere spelled out the consequences under different Python implementations (while I don't know for sure, I _expect_ the current docs just say "in normal conditions, the main thread is the thread from which the Python interpreter was started" because it doesn't want to over-specify the behavior in an area nobody really cares about).
历史
日期 用户 动作 参数
2017-09-20 02:28:41tim.peters修改recipients: + tim.peters, ncoghlan, pitrou, asvetlov, eric.snow
2017-09-20 02:28:41tim.peters修改messageid: <1505874521.69.0.295758998992.issue31517@psf.upfronthosting.co.za>
2017-09-20 02:28:41tim.peters链接issue31517 messages
2017-09-20 02:28:41tim.peters创建