Python 3.5.2 crashers (from PyPy)
Open
Nobody has claimed this yet.
tests
type-crash
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 28883 |
|---|---|
| Nosy | @brettcannon, @arigo, @vstinner, @serhiy-storchaka |
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 2016-12-06.11:49:47.741>
labels = ['type-crash']
title = 'Python 3.5.2 crashers (from PyPy)'
updated_at = <Date 2018-02-25.12:58:11.810>
user = 'https://github.com/arigo'
bugs.python.org fields:
activity = <Date 2018-02-25.12:58:11.810>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2016-12-06.11:49:47.741>
creator = 'arigo'
dependencies = []
files = []
hgrepos = []
issue_num = 28883
keywords = []
message_count = 9.0
messages = ['282518', '282519', '282520', '282521', '282522', '282523', '282525', '282564', '312809']
nosy_count = 4.0
nosy_names = ['brett.cannon', 'arigo', 'vstinner', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue28883'
versions = ['Python 3.5']
Linked PRs
- gh-131642
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 by reading the original report at bugs.python.org issue 28883 and reviewing linked PR gh-131642. Identify the reported Python 3.5.2 crash cases and confirm whether the linked work addresses them; done means the relevant crashers are resolved or clearly reproduced with an agreed fix path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100