ImportError: bad magic number in ... does not indicate where is that file located
Open
Nobody has claimed this yet.
3.11
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 46835 |
|---|---|
| Nosy | @brettcannon, @encukou, @hroncok |
| 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 2022-02-23.12:43:36.296>
labels = ['type-feature', 'library', '3.11']
title = 'ImportError: bad magic number in ... does not indicate where is that file located'
updated_at = <Date 2022-02-24.20:09:00.809>
user = 'https://github.com/hroncok'
bugs.python.org fields:
activity = <Date 2022-02-24.20:09:00.809>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2022-02-23.12:43:36.296>
creator = 'hroncok'
dependencies = []
files = []
hgrepos = []
issue_num = 46835
keywords = ['patch']
message_count = 3.0
messages = ['413788', '413789', '413815']
nosy_count = 3.0
nosy_names = ['brett.cannon', 'petr.viktorin', 'hroncok']
pr_nums = ['31534']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46835'
versions = ['Python 3.11']
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
The issue identifies the CPython Lib component and Python 3.11, but names no source file or test. Review the referenced PR python/cpython#31534 first, then locate the relevant import-error entry point; done means the bad-magic-number error identifies the file location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100