homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients techtonik, vstinner
Date 2011年03月22日.11:16:25
SpamBayes Score 1.4464454e-05
Marked as misclassified No
Message-id <1300792585.82.0.976761051719.issue11633@psf.upfronthosting.co.za>
In-reply-to
Content
printtest2.py displays directly "Processing.. " on Windows, but not on Linux. It looks like stdout is not buffered on Windows, which looks like a bug to bug :-) I think that it is safer to always call sys.stdout.flush() to ensure that your message is directly displayed. With Python 2, you can use -u flag (unbuffered output) to avoid the explicit flush, but this is very inefficient (slow).
Python 3 uses line buffers, even with python3 -u, for better performances. If you want to see directly "Processing.. ", as Python 2, call sys.stdout.flush().
It is not a regression, it is a choice to be efficient.
History
Date User Action Args
2011年03月22日 11:16:25vstinnersetrecipients: + vstinner, techtonik
2011年03月22日 11:16:25vstinnersetmessageid: <1300792585.82.0.976761051719.issue11633@psf.upfronthosting.co.za>
2011年03月22日 11:16:25vstinnerlinkissue11633 messages
2011年03月22日 11:16:25vstinnercreate

AltStyle によって変換されたページ (->オリジナル) /