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 rbcollins
Recipients giampaolo.rodola, loewis, pitrou, r.david.murray, rbcollins, serhiy.storchaka, vajrasky
Date 2015-07-25.19:11:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1437851473.56.0.44418278698.issue10388@psf.upfronthosting.co.za>
In-reply-to
Content
The man page for setspent says this:
"The functions that return a pointer return NULL if no more entries are available or if an error occurs during processing.  The functions  which
       have int as the return value return 0 for success and -1 for failure, with errno set to indicate the cause of the error.

       For the nonreentrant functions, the return value may point to static area, and may be overwritten by subsequent calls to these functions.

       The reentrant functions return zero on success.  In case of error, an error number is returned.

"

-> that is, setspent's interaction with errno is undefined, at least on Linux. I'm a little worried about whether this may pickup false errors as a result.
History
Date User Action Args
2015-07-25 19:11:13rbcollinssetrecipients: + rbcollins, loewis, pitrou, giampaolo.rodola, r.david.murray, serhiy.storchaka, vajrasky
2015-07-25 19:11:13rbcollinssetmessageid: <1437851473.56.0.44418278698.issue10388@psf.upfronthosting.co.za>
2015-07-25 19:11:13rbcollinslinkissue10388 messages
2015-07-25 19:11:13rbcollinscreate