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 martin.panter
Recipients BreamoreBoy, ajaksu2, giampaolo.rodola, loewis, martin.panter, mdr0, nnorwitz, r.david.murray, sable, wiggin15
Date 2015-12-05.10:08:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1449310087.13.0.421210829222.issue9917@psf.upfronthosting.co.za>
In-reply-to
Content
Are there platforms where rlim_t is signed? Posix defines it as unsigned: <http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_resource.h.html>.

Also there are subtle differences between the PyLong_AsUnsigned[. . .] and the current signed versions. The unsigned version does not call __int__() so you would no longer be able to pass a float().

Also this could cause compatibility problems with code that was written for earlier documentation, which said to use -1 to mean unlimited. Perhaps that is why the code has rlim_* & RLIM_INFINITY masking.
History
Date User Action Args
2015-12-05 10:08:07martin.pantersetrecipients: + martin.panter, loewis, nnorwitz, mdr0, sable, giampaolo.rodola, ajaksu2, r.david.murray, BreamoreBoy, wiggin15
2015-12-05 10:08:07martin.pantersetmessageid: <1449310087.13.0.421210829222.issue9917@psf.upfronthosting.co.za>
2015-12-05 10:08:07martin.panterlinkissue9917 messages
2015-12-05 10:08:06martin.pantercreate