pyexpat.errors doesn't have __spec__ and __loader__ set
Open
Nobody has claimed this yet.
topic-importlib
topic-XML
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29830 |
|---|---|
| Nosy | @brettcannon, @ncoghlan, @ericsnowcurrently, @manueljacob |
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-03-16.22:35:12.850>
labels = []
title = "pyexpat.errors doesn't have __spec__ and __loader__ set"
updated_at = <Date 2017-03-19.11:22:38.569>
user = 'https://github.com/manueljacob'
bugs.python.org fields:
activity = <Date 2017-03-19.11:22:38.569>
actor = 'ncoghlan'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2017-03-16.22:35:12.850>
creator = 'mjacob'
dependencies = []
files = []
hgrepos = []
issue_num = 29830
keywords = []
message_count = 5.0
messages = ['289737', '289773', '289774', '289824', '289845']
nosy_count = 4.0
nosy_names = ['brett.cannon', 'ncoghlan', 'eric.snow', 'mjacob']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue29830'
versions = []
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
No file or test is named in the issue. Start by reproducing the missing spec and loader attributes on pyexpat.errors, then trace how that module is imported and compare it with a working extension module. Done means pyexpat.errors exposes both attributes correctly with regression coverage.
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