Skip to content

Py3k's print() flushing problem #45741

@wojtekwalczak

Description

@wojtekwalczak
BPO 1400
Nosy @gvanrossum

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 = 'https://github.com/gvanrossum'
closed_at = <Date 2007-12-06.01:04:52.428>
created_at = <Date 2007-11-07.18:36:11.138>
labels = ['type-bug', 'build']
title = "Py3k's print() flushing problem"
updated_at = <Date 2008-01-06.22:29:45.282>
user = 'https://bugs.python.org/wojtekwalczak'

bugs.python.org fields:

activity = <Date 2008-01-06.22:29:45.282>
actor = 'admin'
assignee = 'gvanrossum'
closed = True
closed_date = <Date 2007-12-06.01:04:52.428>
closer = 'gvanrossum'
components = ['Build']
creation = <Date 2007-11-07.18:36:11.138>
creator = 'wojtekwalczak'
dependencies = []
files = []
hgrepos = []
issue_num = 1400
keywords = []
message_count = 5.0
messages = ['57215', '57255', '57284', '58206', '58236']
nosy_count = 2.0
nosy_names = ['gvanrossum', 'wojtekwalczak']
pr_nums = []
priority = 'high'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue1400'
versions = ['Python 3.0']

Metadata

Metadata

Assignees

Labels

buildThe build process and cross-buildtype-bugAn unexpected behavior, bug, or error
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions