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 nafur
Recipients nafur
Date 2021-02-02.12:52:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1612270361.12.0.132616199639.issue43101@roundup.psfhosted.org>
In-reply-to
Content
While the documentation always (as in: at least since 3.5) required to pass "a tuple (soft, hard) of two integers" to resource.setrlimit(), passing floats worked just fine until 3.9.
This behavior was deprecated in 3.8 and removed in 3.10.

I see that the implementation was merely fixed to do what the documentation says. Nevertheless, I think this change of behavior should be mentioned in the documentation.

In my use-case for resource (within preexec_fn of subprocess.Popen), this deprecation warning only showed up in 3.9 for some reason (as you can see here: https://github.com/nafur/python-playground/runs/1814573503) and is now hidden by a generic "subprocess.SubprocessError: Exception occurred in preexec_fn." message.
A hint in the documentation would have helped significantly...
History
Date User Action Args
2021-02-02 12:52:41nafursetrecipients: + nafur
2021-02-02 12:52:41nafursetmessageid: <1612270361.12.0.132616199639.issue43101@roundup.psfhosted.org>
2021-02-02 12:52:41nafurlinkissue43101 messages
2021-02-02 12:52:40nafurcreate