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 mark.dickinson
Recipients georg.brandl, mark.dickinson, vstinner
Date 2009-05-08.21:15:28
SpamBayes Score 1.1305715e-08
Marked as misclassified No
Message-id <1241817330.7.0.132008015929.issue5933@psf.upfronthosting.co.za>
In-reply-to
Content
Applied in r72479, r72481, r72482, r72483.

As a side note, I'm not 100% convinced of the correctness of the resource_setrlimit code.  If rlim_t is smaller than an unsigned long then input values might be wrapped to a smaller 
value (by the implicit long -> rlim_t conversion) when they should be signaling 
OverflowError instead.  Perhaps there should be a bunch of PySAFE_DOWNCASTs here?

Or maybe rlim_t is never smaller than a long in practice.

About RLIM_INFINITY:  I can't find it documented anywhere that RLIM_INFINITY is (rlim_t)-1, 
though I dare say that's true on many platforms.  Still, it doesn't seem like a safe 
assumption.
History
Date User Action Args
2009-05-08 21:15:30mark.dickinsonsetrecipients: + mark.dickinson, georg.brandl, vstinner
2009-05-08 21:15:30mark.dickinsonsetmessageid: <1241817330.7.0.132008015929.issue5933@psf.upfronthosting.co.za>
2009-05-08 21:15:28mark.dickinsonlinkissue5933 messages
2009-05-08 21:15:28mark.dickinsoncreate