SourceLoader uses stale bytecode in case of equal mtime seconds
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reading the SourceLoader implementation and reviewing the referenced python/cpython#3963 pull request. Confirm the current behavior around equal mtime seconds and identify the existing interpreter tests that cover bytecode loading; done means SourceLoader no longer uses stale bytecode in that case.
Written by the indexing model from the issue text.
Description
| BPO | 31772 |
|---|---|
| Nosy | @brettcannon, @ncoghlan, @ericsnowcurrently, @akvadrako, @iritkatriel |
| 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 2017-10-12.13:43:00.313>
labels = ['interpreter-core', 'type-bug', '3.7']
title = 'SourceLoader uses stale bytecode in case of equal mtime seconds'
updated_at = <Date 2021-06-18.20:55:53.770>
user = 'https://github.com/akvadrako'
bugs.python.org fields:
activity = <Date 2021-06-18.20:55:53.770>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2017-10-12.13:43:00.313>
creator = 'akvadrako'
dependencies = []
files = []
hgrepos = []
issue_num = 31772
keywords = ['patch']
message_count = 18.0
messages = ['304236', '304279', '304285', '304305', '304310', '304311', '304312', '304314', '304316', '304320', '304349', '304373', '304464', '395960', '396025', '396034', '396080', '396086']
nosy_count = 5.0
nosy_names = ['brett.cannon', 'ncoghlan', 'eric.snow', 'akvadrako', 'iritkatriel']
pr_nums = ['3963']
priority = 'normal'
resolution = 'fixed'
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue31772'
versions = ['Python 3.7']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
CSCfi/sd-search-api#39 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
StevenBlack/hosts#3255 ·