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 Arfrever, BreamoreBoy, ezio.melotti, jpe, makegho, steve.dower, tim.golden, vstinner, zach.ware
Date 2014-06-23.09:48:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403516885.17.0.957196120218.issue16587@psf.upfronthosting.co.za>
In-reply-to
Content
"In C++ this often means using std::wstring and std::wcout. Maybe these are more common than wprintf? In any case the console output breaks as Py_Initialize hijacks the host application's standard output streams which sounds quite illegitimate to me."

On Linux, std::wcout doesn't use wprintf(). Do you mean that std::wcout also depends on the "mode" of stdout (_setmode)?
History
Date User Action Args
2014-06-23 09:48:05vstinnersetrecipients: + vstinner, jpe, tim.golden, ezio.melotti, Arfrever, BreamoreBoy, zach.ware, steve.dower, makegho
2014-06-23 09:48:05vstinnersetmessageid: <1403516885.17.0.957196120218.issue16587@psf.upfronthosting.co.za>
2014-06-23 09:48:05vstinnerlinkissue16587 messages
2014-06-23 09:48:05vstinnercreate