Changing interpreter's deafult output/error streams

[Ira]

Hi,

Using an embedded interpreter, how do I change it's default output streams
(specifically the one used by PyErr_Print() which I'm guessing is the
default error stream)?

Cheers,
Ira

[Michael Hudson]

"Ira" <sh******@gmail.com> writes:

Using an embedded interpreter, how do I change it's default output
streams (specifically the one used by PyErr_Print() which I'm
guessing is the default error stream)?

It looks as though it writes to stderr unconditionally. But most of
the reasons for ended up in PyErr_Print can be intercepted at a higher
level (I think -- I mean sys.excepthook & co here).

Cheers,
mwh

--
ARTHUR: Yes. It was on display in the bottom of a locked filing
cabinet stuck in a disused lavatory with a sign on the door
saying "Beware of the Leopard".
-- The Hitch-Hikers Guide to the Galaxy, Episode 1

[Ira]

OK let me rephrase,

the standard error stream (and if I'm not mistaken also the one that
PyErr_Print() writes to) is the python object sys.stderr. Now say I'd go
ahead and write the following in python...

SomeNewStreamOrFileOrWhateverItIs = new stream
sys.stderr = SomeNewStreamOrFileOrWhateverItIs

I can go ahead and do the exact same thing from the C source code. All I
need to do is to figure out how to wrap a c-style FILE* with a PyObject, And
PySys_SetObjet("stderr", newstream);

I'm very new to python so that might be nonsense but it appeals to my
programmer's common sense. Can anyone tell me how to do this?
"Michael Hudson" <mw*@python.net> wrote in message
news:m2************@82-33-185-193.cable.ubr01.azte.blueyonder.co.uk...

"Ira" <sh******@gmail.com> writes:

Using an embedded interpreter, how do I change it's default output
streams (specifically the one used by PyErr_Print() which I'm
guessing is the default error stream)?

It looks as though it writes to stderr unconditionally. But most of
the reasons for ended up in PyErr_Print can be intercepted at a higher
level (I think -- I mean sys.excepthook & co here).

Cheers,
mwh

--
ARTHUR: Yes. It was on display in the bottom of a locked filing
cabinet stuck in a disused lavatory with a sign on the door
saying "Beware of the Leopard".
-- The Hitch-Hikers Guide to the Galaxy, Episode 1
--
http://mail.python.org/mailman/listinfo/python-list

[Robert Kern]

Ira wrote:

OK let me rephrase,

the standard error stream (and if I'm not mistaken also the one that
PyErr_Print() writes to) is the python object sys.stderr. Now say I'd go
ahead and write the following in python...

SomeNewStreamOrFileOrWhateverItIs = new stream
sys.stderr = SomeNewStreamOrFileOrWhateverItIs

I can go ahead and do the exact same thing from the C source code. All I
need to do is to figure out how to wrap a c-style FILE* with a PyObject, And
PySys_SetObjet("stderr", newstream);

I'm very new to python so that might be nonsense but it appeals to my
programmer's common sense. Can anyone tell me how to do this?

http://docs.python.org/api/fileObjects.html

--
Robert Kern
rk***@ucsd.edu

"In the fields of hell where the grass grows high
Are the graves of dreams allowed to die."
-- Richard Harter

[Ira]

OK let me rephrase,

the standard error stream (and if I'm not mistaken also the one that
PyErr_Print() writes to) is the python object sys.stderr. Now say I'd go
ahead and write the following in python...

SomeNewStreamOrFileOrWhateverItIs = new stream
sys.stderr = SomeNewStreamOrFileOrWhateverItIs

I can go ahead and do the exact same thing from the C source code. All I
need to do is to figure out how to wrap a c-style FILE* with a PyObject, And
PySys_SetObjet("stderr", newstream);

I'm very new to python so that might be nonsense but it appeals to my
programmer's common sense. Can anyone tell me how to do this?
"Michael Hudson" <mw*@python.net> wrote in message
news:m2************@82-33-185-193.cable.ubr01.azte.blueyonder.co.uk...

"Ira" <sh******@gmail.com> writes:

Using an embedded interpreter, how do I change it's default output
streams (specifically the one used by PyErr_Print() which I'm
guessing is the default error stream)?

It looks as though it writes to stderr unconditionally. But most of
the reasons for ended up in PyErr_Print can be intercepted at a higher
level (I think -- I mean sys.excepthook & co here).

Cheers,
mwh

--
ARTHUR: Yes. It was on display in the bottom of a locked filing
cabinet stuck in a disused lavatory with a sign on the door
saying "Beware of the Leopard".
-- The Hitch-Hikers Guide to the Galaxy, Episode 1
--
http://mail.python.org/mailman/listinfo/python-list

[Michael Hudson]

"Ira" <sh******@gmail.com> writes:

OK let me rephrase,

the standard error stream (and if I'm not mistaken also the one that
PyErr_Print() writes to) is the python object sys.stderr. Now say I'd go
ahead and write the following in python...

Ah, OK, I think you're mistaken, and PyErr_Print prints to the C level
FILE* stderr (I agree my first post was confusing on this point, sorry
about that...).

Cheers,
mwh

--
<Acapnotic> jemfinch: What's to parse? A numeric code, perhaps a
chicken, and some arguments
-- from Twisted.Quotes

[Robert Kern]

Michael Hudson wrote:

"Ira" <sh******@gmail.com> writes:

OK let me rephrase,

the standard error stream (and if I'm not mistaken also the one that
PyErr_Print() writes to) is the python object sys.stderr. Now say I'd go
ahead and write the following in python...

Ah, OK, I think you're mistaken, and PyErr_Print prints to the C level
FILE* stderr (I agree my first post was confusing on this point, sorry
about that...).

No, it doesn't. It grabs the appropriate object from sys.stderr.

--
Robert Kern
rk***@ucsd.edu

"In the fields of hell where the grass grows high
Are the graves of dreams allowed to die."
-- Richard Harter

[Michael Hudson]

Robert Kern <rk***@ucsd.edu> writes:

Michael Hudson wrote:

"Ira" <sh******@gmail.com> writes:

OK let me rephrase,

the standard error stream (and if I'm not mistaken also the one that
PyErr_Print() writes to) is the python object sys.stderr. Now say I'd go
ahead and write the following in python...

Ah, OK, I think you're mistaken, and PyErr_Print prints to the C
level
FILE* stderr (I agree my first post was confusing on this point, sorry
about that...).

No, it doesn't. It grabs the appropriate object from sys.stderr.

Ah, you're right, I somehow ended up reading PySys_WriteStderr...

Cheers,
mwh

--
The only problem with Microsoft is they just have no taste.
-- Steve Jobs, (From _Triumph of the Nerds_ PBS special)
and quoted by Aahz on comp.lang.python