➜

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 pitrou
Recipients giampaolo.rodola, neologix, petri.lehtinen, pitrou, santoso.wijaya, socketpair
Date 2011-07-26.21:34:27
SpamBayes Score 0.00034955872
Marked as misclassified No
Message-id <1311715978.8406.3.camel@localhost.localdomain>
In-reply-to <CAH_1eM3ji+ecQvF+3Y0y+6pg-rp6PNANBEDk-OEgr_AiY5VjDg@mail.gmail.com>
Content 
> When you join a thread which hasn't been started, you get an
> exception, not a deadlock.

But we don't have a deadlock here: another thread could perfectly well
call serve_forever() in the meantime and shutdown() should then return
after having stopped the event loop.

My point is that changing semantics may break existing software, without
there being a clear benefit in doing so.
History
Date User Action Args
2011-07-26 21:34:28pitrousetrecipients: + pitrou, giampaolo.rodola, neologix, santoso.wijaya, socketpair, petri.lehtinen
2011-07-26 21:34:27pitroulinkissue12463 messages
2011-07-26 21:34:27pitroucreate