[IronPython] engine.Dispose closes the stdout stream

[Dino Viehland]

I've looked into this on our side the guidance seems to be that we should add an overload of Set* that allows you to specify if we should close the stream or not.  This is analogous to the GZipStream constructor (http://msdn2.microsoft.com/en-us/library/system.io.compression.gzipstream.gzipstream.aspx).

I've opened bug #6144 to track this (http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=6144).


-----Original Message-----
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Stute, Detlef ALRT/EEG4 (Fa. epos)
Sent: Wednesday, November 29, 2006 3:18 AM
To: users at lists.ironpython.com
Subject: [IronPython] engine.Dispose closes the stdout stream

Hi all,
I redirect the stdout/err ... when I start the python engine


engine = new PythonEngine(eo);

// create stream to get the messages from the python engine
stream = new NotifyingStream();
engine.SetStandardOutput(stream);
engine.SetStandardError(stream);

When I call engine.Dispose() there the streams are closed. Is that the
way the engine should do?
It did not open the streams why does it close them?
Best regards
Detlef Stute
www.seatec-gmbh.com
_______________________________________________
users mailing list
users at lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com