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 akira
Recipients CristianCantoro, akira, georg.brandl, gps, pitrou, r.david.murray
Date 2014-08-28.16:16:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1409242618.83.0.120581445019.issue22277@psf.upfronthosting.co.za>
In-reply-to
Content
open(url, stdout=DEVNULL) won't work on Windows (os.startfile()) and OS
X (AppleScript) by default.

UnixBrowser already suppresses the output when it is safe, if
self.redirect_stdout=True and self.background=True are set.

Also, open(url, stdout=DEVNULL) would probably break text-browsers such
as elinks (e.g., they are run when $DISPLAY environment variable is not set).

What left: Unix browsers for which webbrowser doesn't think that it is
safe to suppress the output. If webbrowser allows the output when it
shouldn't then it could be fixed on case by case basis and/or maybe some
mechanism could be provided to override the webbrowser choice e.g.,
BaseBrowser.suppress_output attribute that defaults to None (let
webbrowser decide).

webbrowser is a high-level interface; stdout/stderr from subprocess are
too low-level for open() function (inventing your own stdout/stderr
values is even worse).
History
Date User Action Args
2014-08-28 16:16:58akirasetrecipients: + akira, georg.brandl, pitrou, gps, r.david.murray, CristianCantoro
2014-08-28 16:16:58akirasetmessageid: <1409242618.83.0.120581445019.issue22277@psf.upfronthosting.co.za>
2014-08-28 16:16:58akiralinkissue22277 messages
2014-08-28 16:16:58akiracreate