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 Zahari.Dim
Recipients Zahari.Dim, martin.panter, r.david.murray
Date 2016-06-02.16:01:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CANx7HSbhKyyxu=R5Uc65uTj2C7zHa3F6Geu2DYPoWX6RNwh=Ug@mail.gmail.com>
In-reply-to <1462658671.17.0.304700333649.issue24500@psf.upfronthosting.co.za>
Content
Considering Python is used often to interact with lower level
languages, it seems interesting to have the ability to control the
"real" standard output and error that those languages use. Note that
redirecting to /dev/null is only one possible application of this
feature. Others would be for example linking the stout to the logging
module.

Specifically regarding redirecting to /dev/null, in my experience this
would be fairly useful In scientific software where low level code
tends to be used on scientific merits rather than on how much control
it has over verbosity.

On Sun, May 8, 2016 at 12:04 AM, Martin Panter <report@bugs.python.org> wrote:
>
> Martin Panter added the comment:
>
> Is it really common to have a C wrapper with undesirable output? I suspect there is not much demand for this feature. Maybe this would be better outside of Python’s standard library.
>
> ----------
> nosy: +martin.panter
> status: open -> languishing
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue24500>
> _______________________________________
History
Date User Action Args
2016-06-02 16:01:09Zahari.Dimsetrecipients: + Zahari.Dim, r.david.murray, martin.panter
2016-06-02 16:01:09Zahari.Dimlinkissue24500 messages
2016-06-02 16:01:09Zahari.Dimcreate