[issue9917] resource max value represented as signed when should be unsigned
R. David Murray
report at bugs.python.org
Wed Sep 22 15:13:47 CEST 2010
R. David Murray <rdmurray at bitdance.com> added the comment:
And here is Martin's summary of the issue:
I think we really should create new issues for any remaining problems.
AFAICT, the remaining problems are:
- resource.RLIM_INFINITY is -1 on Linux, when it is meant to be
a really large value
- (as you reported) getrlimit returns -1 to indicate RLIM_INFINITY.
I think the core of the problem is that the resource module considers
rlim_t to be a signed type (or at least representable in "long long").
Using FromUnsignedLongLong in the appropriate place might solve the
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list