From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] standardizing output
Date: Thu, 8 Oct 2015 20:38:25 -0400 [thread overview]
Message-ID: <20151009003825.GD29146@vapier.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
how do people feel about killing off the use of "print" everywhere and
moving to the standard logging module ? biggest advantages in my mind:
- we get much easier control over where the output goes (file/stdout/...)
- we force people to select a level (info/warning/error)
- we get standardized output
- we can more easily control the output (debug/verbose/etc...)
- we can include module/func/line info transparently in debug modes
- we can exit transparently on fatal/critical messages (rather than using
die/exit/etc... directly)
- we can colorize warnings/errors transparently
- we get py3 compat for free (all current print usage is py2-only)
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2015-10-09 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 0:38 Mike Frysinger [this message]
2015-10-09 1:24 ` [gentoo-catalyst] standardizing output Brian Dolbec
2015-10-09 6:04 ` Mike Frysinger
2015-10-09 15:26 ` Brian Dolbec
2015-10-09 16:01 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151009003825.GD29146@vapier.lan \
--to=vapier@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox