Issue 23861: Make stdprinter use DebugOutputString when no stdout/stderr available (original) (raw)

Issue23861

➜

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.

classification

Title:	Make stdprinter use DebugOutputString when no stdout/stderr available
Type:	Stage:
Components:	Windows	Versions:	Python 3.5

process

Status:	open	Resolution:
Dependencies:		Superseder:
Assigned To:		Nosy List:	steve.dower, tim.golden, zach.ware
Priority:	normal	Keywords:

Created on 2015-04-03 18:55 by steve.dower, last changed 2022-04-11 14:58 by admin.

Messages (3)
msg240025 - (view)	Author: Steve Dower (steve.dower) *	Date: 2015-04-03 18:55
Currently we initialize stdprinter while initializing and terminate if we can't access std streams. We should always write to DebugOutputString on Windows (only does anything if a debugger is attached) and avoid terminating in this case.
msg240064 - (view)	Author: Tim Golden (tim.golden) *	Date: 2015-04-04 11:18
Are we talking about re-implementing StdPrinter in terms of OutputDebugString? (Either always, on Windows, or as a fallback?)
msg240069 - (view)	Author: Steve Dower (steve.dower) *	Date: 2015-04-04 14:05
There's just a couple of places to add calls to OutputDebugString, plus we need to make creation always succeed on Windows. Not a huge change - it'll still write to the standard stream if it's there.