resource.setrlimit() should raise PermissionError
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38480 |
|---|---|
| Nosy | @giampaolo |
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2019-10-15.07:34:20.121>
labels = ['library', '3.9']
title = 'resource.setrlimit() should raise PermissionError'
updated_at = <Date 2019-10-15.16:12:16.221>
user = 'https://github.com/giampaolo'
bugs.python.org fields:
activity = <Date 2019-10-15.16:12:16.221>
actor = 'giampaolo.rodola'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-10-15.07:34:20.121>
creator = 'giampaolo.rodola'
dependencies = []
files = []
hgrepos = []
issue_num = 38480
keywords = ['patch']
message_count = 2.0
messages = ['354701', '354741']
nosy_count = 1.0
nosy_names = ['giampaolo.rodola']
pr_nums = ['16804']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue38480'
versions = ['Python 3.9']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the resource.setrlimit() entry point and review pull request #16804, which is referenced in the issue. Verify the resulting behavior for permission failures and confirm that the change is covered by the relevant tests before considering the issue complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100