[issue1400] Py3k's print() flushing problem

Guido van Rossum added the comment: Committed revision 59379. This adds proper line_buffering behavior. -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ _

[issue1400] Py3k's print() flushing problem

Guido van Rossum added the comment: In r59341 I added a flush of stdout and stderr at the end of each command that restores the following behavior: >>> n = sys.stdout.write('X') X>>> I still need to change io.py to properly implement line buffering though; the current implementation is wrong.

[issue1400] Py3k's print() flushing problem

Changes by Christian Heimes: -- assignee: -> gvanrossum __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http

[issue1400] Py3k's print() flushing problem

Guido van Rossum added the comment: I don't think anything was accepted yet. -- nosy: +gvanrossum resolution: accepted -> __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1400] Py3k's print() flushing problem

Wojciech Walczak added the comment: 2007/11/8, admin <[EMAIL PROTECTED]>: > -- > keywords: +py3k > priority: -> high > resolution: -> accepted Which resolution was accepted? Wojtek Walczak __ Tracker <[EMAIL PROTECTED]>

[issue1400] Py3k's print() flushing problem

Changes by Christian Heimes: -- keywords: +py3k priority: -> high resolution: -> accepted __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-li

[issue1400] Py3k's print() flushing problem

New submission from Wojciech Walczak: py3k's print() is not flushing when the string's length is 1 byte long and 'end' parameter is set to ''. Example: >>> print('x',end='') # it should print 'x' but it does nothing >>> print('') # we have to call second print() to get buffers flushed x >>> The