On Thu, Oct 05, 2000 at 01:10:14PM -0400, Chuck Esterbrook wrote:
> At 02:13 AM 10/5/00 -0400, Dan Green wrote:
> >Any chance we could look at replacing the thousands of print statements all
> >over WebKit with something like self.log('')? I ask because,
> >a) being able to log to a file is nice (yes, I know I can redirect, see
> >point b)
> >b) I've started writing an actual application server that bypasses the
> > entirely, and just uses fastCGI. Mucking about with stdin and stdout in a
> > fastCGI environment is a good way to make your computer cross with you.
> Actually, we chose for "print" statements to go the console on purpose for
> easy debugging. Even if we could do self.log() in servlets, in a rich web
> application you will have plenty of non-servlet classes.
> I'd really like to stick with print going to console.
> I wonder, in Python when we do things like set sys.stdout to a StringIO
> we're not really modifying the C/system stdout, right? Just the 'stdout'
> attribute of 'sys' which gets used by 'print'.
> Doesn't seem like FastCGI should be mucked up over this. Also, doesn't the
> existing FastCGI adapter work fine?
> I guess I'm wondering what the exact nature of the problem is and how it's
What you experienced was a phenomenon known as "Dan talking out of his a**.".
Several training companies provide courses on how to ignore me.