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 tim.peters
Recipients Tamas.K, csernazs, grahamd, jcea, ncoghlan, neologix, pitrou, python-dev, tim.peters
Date 2013-09-07.00:49:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378515002.44.0.6354335369.issue18808@psf.upfronthosting.co.za>
In-reply-to
Content
All the timeout args are great!  I wish Python had always had them :-)

Back to the pain at hand, it's not the number of lines of code that rubs me the wrong way, but the sheer obscurity of it all.  This handful of lines is - of necessity - sprayed across two C code files, a C header file, and a Python module.  That makes it very hard (for anyone but you - LOL) to reconstruct the _intent_ of it all.

I'm adding another patch, which is your threadstate_join_2.patch but with a new comment block (in pystate.h) spelling out the rationale behind it all.  I can live with that ;-)
History
Date User Action Args
2013-09-07 00:50:02tim.peterssetrecipients: + tim.peters, jcea, csernazs, ncoghlan, pitrou, grahamd, neologix, python-dev, Tamas.K
2013-09-07 00:50:02tim.peterssetmessageid: <1378515002.44.0.6354335369.issue18808@psf.upfronthosting.co.za>
2013-09-07 00:50:02tim.peterslinkissue18808 messages
2013-09-07 00:50:01tim.peterscreate