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 jwilk
Recipients jwilk
Date 2015-08-24.15:25:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440429911.87.0.822286157872.issue24924@psf.upfronthosting.co.za>
In-reply-to
Content
The safe_get_max_fd() (in Modules/_posixsubprocess.c) is documented to be async-signal-safe.

However, this function calls sysconf().
sysconf() was guaranteed to be async-singal-safe in SUSv3, but it's no longer in SUSv4.

I don't think it's going to be a problem in practice, but it's probably worth adding a clarification comment.
History
Date User Action Args
2015-08-24 15:25:11jwilksetrecipients: + jwilk
2015-08-24 15:25:11jwilksetmessageid: <1440429911.87.0.822286157872.issue24924@psf.upfronthosting.co.za>
2015-08-24 15:25:11jwilklinkissue24924 messages
2015-08-24 15:25:11jwilkcreate