Message 196192 - Python tracker

➜

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	Drekin
Recipients	Drekin
Date	2013-08-26.09:05:07
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1377507907.91.0.430796932988.issue18838@psf.upfronthosting.co.za>
In-reply-to

Content
On Windows, Python 3.3.2, when I run Python as a subprocess via Popen("py -i somescript.py", stdin=PIPE, stdout=PIPE, stderr=PIPE).communicate() and somescript.py ends with exception, there is first interactive promt ">>>" in stderr output and then the traceback which is reversed to standard order when somescript.py is run interactively directly. Corresponding StackOverflow question: http://stackoverflow.com/questions/18419724/position-of-prompt-in-stderr-after-systemexit .

On Windows, Python 3.3.2, when I run Python as a subprocess via Popen("py -i somescript.py", stdin=PIPE, stdout=PIPE, stderr=PIPE).communicate() and somescript.py ends with exception, there is first interactive promt ">>>" in stderr output and then the traceback which is reversed to standard order when somescript.py is run interactively directly.

Corresponding StackOverflow question: http://stackoverflow.com/questions/18419724/position-of-prompt-in-stderr-after-systemexit .

History
Date	User	Action	Args
2013-08-26 09:05:07	Drekin	set	recipients: + Drekin
2013-08-26 09:05:07	Drekin	set	messageid: <1377507907.91.0.430796932988.issue18838@psf.upfronthosting.co.za>
2013-08-26 09:05:07	Drekin	link	issue18838 messages
2013-08-26 09:05:07	Drekin	create