python -m doctest script_file_with_no_py_extension produces confusing NameErrors
Open
Nobody has claimed this yet.
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27447 |
|---|---|
| Nosy | @bitdancer |
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-07-04.09:54:32.595>
labels = ['type-bug', 'library']
title = 'python -m doctest script_file_with_no_py_extension produces confusing NameErrors'
updated_at = <Date 2016-07-04.17:12:00.973>
user = 'https://bugs.python.org/towb'
bugs.python.org fields:
activity = <Date 2016-07-04.17:12:00.973>
actor = 'towb'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-07-04.09:54:32.595>
creator = 'towb'
dependencies = []
files = []
hgrepos = []
issue_num = 27447
keywords = []
message_count = 3.0
messages = ['269781', '269790', '269799']
nosy_count = 2.0
nosy_names = ['r.david.murray', 'towb']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27447'
versions = ['Python 3.6']
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 reproducing the python -m doctest command with a script file that has no .py extension. Then inspect the doctest module's command-line entry point and determine why the reported NameErrors are confusing. Done means the same input produces an understandable result, with regression coverage added if an existing test location is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100