This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author theller
Recipients doughellmann, eric.smith, exarkun, georg.brandl, michael.foord, ncoghlan, pitrou, r.david.murray, theller, vinay.sajip
Date 2009-09-22.19:01:53
SpamBayes Score 2.8370048e-05
Marked as misclassified No
Message-id <4AB91F1D.4090100@ctypes.org>
In-reply-to <1253566957.11.0.0207988326745.issue6958@psf.upfronthosting.co.za>
Content
> Jean-Paul Calderone:
> 
> How about putting this into the logging module instead?  Instead of
> "python <logging options> <program> <program options>", making it
> "python -m logging <logging options> <program> <program options".
> 
> This:
> 
>   * involves no changes to the core interpreter
>   * only requires Python to be written, not C
>   * Lets other VMs benefit from the feature immediately
>   * Follows what seems to be the emerging convention for this kind of
> (eg pdb, unittest)
>   * Still allows logging to be configured for arbitrary programs that
> wouldn't otherwise be configurable in this way

This is a very good idea, and fully covers my use case.
History
Date User Action Args
2009-09-22 19:01:55thellersetrecipients: + theller, georg.brandl, vinay.sajip, exarkun, ncoghlan, pitrou, eric.smith, doughellmann, r.david.murray, michael.foord
2009-09-22 19:01:54thellerlinkissue6958 messages
2009-09-22 19:01:54thellercreate