Martin v. Löwis <mar...@v.loewis.de> added the comment: > As a point of information, on my gentoo linux system without > largefile support in the kernel, any value 4294967295 or above > results in getrlimit reporting -1. Any smaller value is set and > reported as itself. (If a sufficiently large value is passed in to > setrlimit, an OverflowError results.)
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 issue. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue678264> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
