➜
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.
Created on 2019-10-15 07:34 by giampaolo.rodola, last changed 2022-04-11 14:59 by admin.
| Pull Requests | |||
|---|---|---|---|
| URL | Status | Linked | Edit |
| PR 16804 | open | giampaolo.rodola, 2019-10-15 16:11 | |
| Messages (2) | |||
|---|---|---|---|
| msg354701 - (view) | Author: Giampaolo Rodola' (giampaolo.rodola) *  |
Date: 2019-10-15 07:34 | |
>>> import resource
>>> high = 300 * 1024 * 1024
>>> resource.setrlimit(resource.RLIMIT_MEMLOCK, (high, high))
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: not allowed to raise maximum limit
>>>
Internally EPERM is translated into ValueError (should have been PermissionError). resource.prlimit(), on the other hand, is not affected (correctly raises PermissionError):
>>> resource.prlimit(os.getpid(), resource.RLIMIT_MEMLOCK, (high, high))
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
PermissionError: [Errno 1] Operation not permitted
It seems 'ValueError' was used in order to provide a more informative error message, but IMO it was a bad call.
Proposal is to change this in 3.9 only, and document it under whatsnew/porting.
|
|||
| msg354741 - (view) | Author: Giampaolo Rodola' (giampaolo.rodola) * |
Date: 2019-10-15 16:12 | |
It turns out there is a similar precedent which was solved in the same way: issue18787. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:21 | admin | set | github: 82661 |
| 2019-10-15 16:12:16 | giampaolo.rodola | set | messages: + msg354741 |
| 2019-10-15 16:11:08 | giampaolo.rodola | set | keywords:
+ patch stage: patch review pull_requests: + pull_request16360 |
| 2019-10-15 07:34:20 | giampaolo.rodola | create | |