Leo Breebaart wrote:
> Also, assume that I have set it up as above. Now I want certain
> other print statements to go to sys.stderr alone. If I understand
> the docs correctly (possibly I don't), the way to do this is to
> start attaching explicit StreamHandlers and whatnot. Whereas with
> print
Leo Breebaart enlightened us with:
> Okay, you say, that's still easy. It's just:
>
> logging.basicConfig(level=logging.DEBUG,
> format='%(message)s')
I always use a separate logger, as per my example. That would then
just require an additional line:
log.setLeveL(logging.DEBUG
Sybren Stuvel <[EMAIL PROTECTED]> writes:
> Leo Breebaart enlightened us with:
> > I think the main reason why I am not using [logging] by
> > default is because, when all is said and done, it still comes
> > easier to me to resort to guarded print statements then to
> > set up and use the loggin
Leo Breebaart enlightened us with:
> I think the main reason why I am not using it by default is because,
> when all is said and done, it still comes easier to me to resort to
> guarded print statements then to set up and use the logging
> machinery.
The logging "machinery" isn't that huge nor is
"alisonken1" <[EMAIL PROTECTED]> writes:
> Leo Breebaart wrote:
>
> > I am writing fairly large console scripts in Python. They
> > have quite a few command-line options, which lead to
> > configuration variables that are needed all over the program
> > (e.g. the "--verbose" option alone is used b
