ListProxy with EventProxy in caused FileNotFoundError: [Errno 2] No such file or directory problem
Open
Nobody has claimed this yet.
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43264 |
|---|---|
| Nosy | @iritkatriel, @show-me-code |
| Files |
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 2021-02-19.08:55:42.000>
labels = ['type-bug']
title = 'ListProxy with EventProxy in caused FileNotFoundError: [Errno 2] No such file or directory problem'
updated_at = <Date 2021-10-18.22:09:59.416>
user = 'https://github.com/show-me-code'
bugs.python.org fields:
activity = <Date 2021-10-18.22:09:59.416>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2021-02-19.08:55:42.000>
creator = 'show-me-code'
dependencies = []
files = ['49819', '49820']
hgrepos = []
issue_num = 43264
keywords = []
message_count = 2.0
messages = ['387295', '404231']
nosy_count = 2.0
nosy_names = ['iritkatriel', 'show-me-code']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue43264'
versions = ['Python 3.6']
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
Begin with the linked server.py and client1.py, then run the example to reproduce the FileNotFoundError involving ListProxy and EventProxy. Confirm the expected proxy behavior and trace the failure before defining a regression check; done means the reported example no longer raises the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100