doctest ignores "from future import print_function"

Open

#67,232 opened on Dec 12, 2014 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 25/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: python
Domain: testing

Research direction

Start by reproducing the doctest behavior described in the title, using the Python 2.7 version listed in the issue. Locate the doctest implementation and its existing tests; done means that doctest correctly honors "from future import print_function" and the relevant regression test passes.

Written by the indexing model from the issue text.

Description

stdlib type-bug

BPO	23043

^{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 2014-12-12.21:28:18.563>
labels = ['type-bug', 'library']
title = 'doctest ignores "from __future__ import print_function"'
updated_at = <Date 2015-02-13.01:26:02.907>
user = 'https://bugs.python.org/fva'

bugs.python.org fields:

activity = <Date 2015-02-13.01:26:02.907>
actor = 'demian.brecht'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-12-12.21:28:18.563>
creator = 'fva'
dependencies = []
files = []
hgrepos = []
issue_num = 23043
keywords = []
message_count = 4.0
messages = ['232577', '233053', '233054', '233055']
nosy_count = 2.0
nosy_names = ['Julien.Palard', 'fva']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue23043'
versions = ['Python 2.7']

Dominant language: Python
Stars: 77.2k
Forks: 36k
Avg merge: 1d 9h
Merged PRs (30d): 558

Contributor guide

Open the contributing 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.

Similar issues

pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
AZ baseline non-refundable credit ordering applies charitable before dependent/family credits, contrary to Forms 140/301 Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

PolicyEngine/policyengine-us#9559 · Opened Sep 21, 2026
google-cloud-php: remove format step from owlbot.py now that librarian runs formatting during generate Open

priority: p3

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

googleapis/librarian#7636 · Opened Sep 21, 2026
[bug] clean-merge parity integration fixtures fail the current approval gate Open

from:qa priority:P2 reliability tech-debt

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

spec-kitty/spec-kitty#4874 · Opened Sep 21, 2026
Document scheduler: manual Run-Once job bypasses max_instances and can run concurrent with the interval pass Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

LearningCircuit/local-deep-research#6722 · Opened Sep 21, 2026

More Python issues

doctest ignores "from __future__ import print_function"