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 steve.dower
Recipients David Hirschfeld, andzn, asvetlov, desbma, eryksun, paul.moore, pitrou, steve.dower, tim.golden, vstinner, zach.ware
Date 2019-06-05.18:56:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559760976.42.0.0760552179314.issue28708@roundup.psfhosted.org>
In-reply-to
Content
> So it's really FD_SETSIZE that matters, and it's a compile-time constant.

The only way this constant can matter is if the array has to end with an empty slot, which doesn't appear to be the case. The pre-compiled function can't tell how you compiled the code calling it, and the only place where FD_SETSIZE is used is in the macros to set them.

Dynamic allocation ought to be just fine, and likely faster for big arrays.
History
Date User Action Args
2019-06-05 18:56:16steve.dowersetrecipients: + steve.dower, paul.moore, pitrou, vstinner, tim.golden, asvetlov, zach.ware, desbma, eryksun, David Hirschfeld, andzn
2019-06-05 18:56:16steve.dowersetmessageid: <1559760976.42.0.0760552179314.issue28708@roundup.psfhosted.org>
2019-06-05 18:56:16steve.dowerlinkissue28708 messages
2019-06-05 18:56:16steve.dowercreate