[issue43101] Add deprecation of float limits for resource to documentation

Mark Dickinson added the comment: Maybe the better fix is to have better reporting of the `preexec_fn` error, so that it's not entirely hidden by the `SubprocessError`? On the other hand, given that `preexec_fn` may be going away entirely soon (see #38435), that may not be worth it. ---

[issue43101] Add deprecation of float limits for resource to documentation

Gereon Kremer added the comment: Hm, I see. For methods that do not intercept exceptions or run code in a different process or alike, the deprecation warning and the TypeError should be sufficient. Given that identifying this issue can be particularly nasty for setrlimit (if used within pre

[issue43101] Add deprecation of float limits for resource to documentation

Mark Dickinson added the comment: Agreed with Serhiy that it's not practical to document all the affected functions. -- ___ Python tracker ___ ___

[issue43101] Add deprecation of float limits for resource to documentation

Serhiy Storchaka added the comment: This change was indirectly documented in What's New for 3.8 (deprecation) https://docs.python.org/3.8/whatsnew/3.8.html#build-and-c-api-changes: """ Functions that convert Python number to C integer like PyLong_AsLong() and argument parsing functions like

[issue43101] Add deprecation of float limits for resource to documentation

Change by Raymond Hettinger : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue43101] Add deprecation of float limits for resource to documentation

New submission from Gereon Kremer : 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 im