Warn when __loader__ != __spec__.loader
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
topic-importlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 31554 |
|---|---|
| Nosy | @warsaw, @brettcannon, @ncoghlan, @ericvsmith, @ericsnowcurrently |
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-09-22.18:42:23.496>
labels = ['3.7', 'type-feature', 'library']
title = 'Warn when __loader__ != __spec__.loader'
updated_at = <Date 2017-12-13.15:57:43.686>
user = 'https://github.com/brettcannon'
bugs.python.org fields:
activity = <Date 2017-12-13.15:57:43.686>
actor = 'eric.smith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-09-22.18:42:23.496>
creator = 'brett.cannon'
dependencies = []
files = []
hgrepos = []
issue_num = 31554
keywords = []
message_count = 1.0
messages = ['302764']
nosy_count = 5.0
nosy_names = ['barry', 'brett.cannon', 'ncoghlan', 'eric.smith', 'eric.snow']
pr_nums = []
priority = 'low'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31554'
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
The issue names no file or test; begin with the loader and spec.loader entry points and determine where their relationship is checked. Add a warning for mismatched values, and add or run tests covering that warning; the issue's recorded stage is "test needed."
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100