R. David Murray added the comment: Thanks for the patch. You got the patch mechanics correct.
I did a little experimenting, and at least on my linux box, the exception is raised for any(*) resource whose hard limit is not unlimited. I'm attaching a revised patch that expresses this. Do you think this provides sufficient clarification? One question I have relates to the use of the word 'infinite'. In the shell, the term 'unlimited' is used, so I'm thinking that's what most people will be familiar with. On the other hand, the man page for the syscall we are wrapping uses the term 'infinite', so one can argue that it is more correct. I'm ambivalent about which term to use. (*) I tested this on NO_PROC, since that's the only other one my shell has a hard limit for, and by setting a hard limit via the shell ulimit command and then using (-1, -1) in the setrlimit call. ---------- Added file: http://bugs.python.org/file29532/setrlimit_doc.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17409> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
