On Wed, Mar 23, 2005 at 06:39:41PM -0500, Fred L. Drake, Jr. wrote:
On Wednesday 23 March 2005 07:40, Oleg Broytmann wrote:
While I'm working on webbrowser... Why do all graphical browsers are
called with their stdout/stderr redirected to /dev/null? Do we really
need to hide problems
Hello!
While I'm working on webbrowser... Why do all graphical browsers are
called with their stdout/stderr redirected to /dev/null? Do we really
need to hide problems from the user? Browsers are usually silent beasts
- they interact with the user using windows, not stdio.
(Text-mode
On Wed, Mar 23, 2005 at 11:59:24AM -0300, Rodrigo Dias Arruda Senra wrote:
Has this same issue been dealt in another stdlib module ?
pydoc.py:
rc = os.system('netscape -remote openURL(%s) ' % url)
if rc: os.system('netscape %s ' % url)
PS. This, of course, should must be fixed - pydoc
Oops...
PS. This, of course, should must be fixed - pydoc must use webbrowser.py!
^^ delete (-:
Oleg.
--
Oleg Broytmannhttp://phd.pp.ru/[EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
On Wednesday 23 March 2005 07:40, Oleg Broytmann wrote:
While I'm working on webbrowser... Why do all graphical browsers are
called with their stdout/stderr redirected to /dev/null? Do we really
need to hide problems from the user? Browsers are usually silent beasts
- they interact with
On Wednesday 23 March 2005 08:25, Rodrigo Dias Arruda Senra wrote:
Under some linux distros (I'm positive for some Mdk releases), Mozilla is
compiled dumping a lot of info to stdout/stderr. Since one of the goals of
webbrowser is to give the end-user a stress-free experience, there goes
On 23 March 2005, Oleg Broytmann said:
I'd like to remove all those redirects. Any opinion?
+0.5. The beauty of Python is that it generally provides thin
wrappers: when writing a convenient wrapper, it's OK to expose the
underlying beast, warts and all.
(I had a minor epiphany about this
