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 fijal
Recipients amaury.forgeotdarc, arigo, fijal, loewis, theller
Date 2008-05-23.14:52:45
SpamBayes Score 0.07483491
Marked as misclassified No
Message-id <1211554370.31.0.0577085616372.issue1798@psf.upfronthosting.co.za>
In-reply-to
Content
On the one hand, no it does not hurt when we're resetting errno before
any call. On the other hand if we try hard "to be like C", it's a bit
strange that we always reset errno (which is on the other hand very good
practice anyway).

IMO it's fine to reset errno before any call, until someone can find
example where it's not good.

Cheers,
fijal
History
Date User Action Args
2008-05-23 14:52:51fijalsetspambayes_score: 0.0748349 -> 0.07483491
recipients: + fijal, loewis, arigo, theller, amaury.forgeotdarc
2008-05-23 14:52:50fijalsetspambayes_score: 0.0748349 -> 0.0748349
messageid: <1211554370.31.0.0577085616372.issue1798@psf.upfronthosting.co.za>
2008-05-23 14:52:49fijallinkissue1798 messages
2008-05-23 14:52:48fijalcreate