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 azanella, hroncok, ned.deily, pitrou
Date 2018-04-22.15:12:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1524409921.86.0.682650639539.issue33329@psf.upfronthosting.co.za>
In-reply-to
Content
> Why not export and use the canonical way of sigemptyset/sigfillset/sigaddset/sigdelset/sigismember instead of pushing for more potential non-conformant code? 

I agree this is the proper fix and that's what I plan to do in Python 3.8.  For Python 3.7 and earlier, though, we cannot add new features anymore, which is why I'm leaning towards a variant of the patch I showed above (which also minimizes the risk for regressions by introducing and using a new API).
History
Date User Action Args
2018-04-22 15:12:01pitrousetrecipients: + pitrou, ned.deily, hroncok, azanella
2018-04-22 15:12:01pitrousetmessageid: <1524409921.86.0.682650639539.issue33329@psf.upfronthosting.co.za>
2018-04-22 15:12:01pitroulinkissue33329 messages
2018-04-22 15:12:01pitroucreate