function changed when pickle bound method object
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37297 |
|---|---|
| Nosy | @rhettinger, @pitrou, @tiran, @asvetlov, @serhiy-storchaka, @maggyero |
| 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 2019-06-16.01:40:57.101>
labels = ['3.7', 'type-bug', 'library']
title = 'function changed when pickle bound method object'
updated_at = <Date 2019-06-17.21:01:20.919>
user = 'https://bugs.python.org/georgexsh'
bugs.python.org fields:
activity = <Date 2019-06-17.21:01:20.919>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-06-16.01:40:57.101>
creator = 'georgexsh'
dependencies = []
files = ['48424']
hgrepos = []
issue_num = 37297
keywords = ['patch']
message_count = 4.0
messages = ['345721', '345776', '345867', '345872']
nosy_count = 7.0
nosy_names = ['rhettinger', 'pitrou', 'christian.heimes', 'asvetlov', 'serhiy.storchaka', 'georgexsh', 'maggyero']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue37297'
versions = ['Python 3.7']
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 linked BPO issue 37297 and the historical 0001-fix-bound-method-reduce-bug.patch file. Reproduce the reported change in function behavior when pickling a bound method, then compare the result with the patch and identify the relevant library tests. Done means the reported behavior is corrected and covered by regression testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100