PyWart: The problem with "print"
Chris Angelico
rosuav at gmail.com
Sun Jun 2 13:34:45 EDT 2013
More information about the Python-list mailing list
Sun Jun 2 13:34:45 EDT 2013
- Previous message (by thread): PyWart: The problem with "print"
- Next message (by thread): PyWart: The problem with "print"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Jun 3, 2013 at 3:30 AM, Andrew Berg <robotsondrugs at gmail.com> wrote: > I don't think you go far enough. Obviously we need way more flexibility. A simple on/off is okay for some things, but a finer granularity > would be really helpful because some things are more important than others. And why stop at stdout/stderr? We need to add a consistent way > to output these messages to files too in case we need to reference them again. The messages should have a consistent format as well. Why add > the same information to each message when it would be much simpler to simply define a default format and insert the real meat of the message > into it? It really seems like we should already have something like this. Hmm..... You have a really good point there. I'm sure I could think of a really good way to do all this, but I'm stuck... it's like there's a log jam in my head... (Okay, maybe I should go to bed now, my puns are getting worse. Considering how late it is, I'll probably sleep like a log.) ChrisA
- Previous message (by thread): PyWart: The problem with "print"
- Next message (by thread): PyWart: The problem with "print"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list