Message92960
| Author | exarkun |
|---|---|
| Recipients | doughellmann, eric.smith, exarkun, georg.brandl, michael.foord, ncoghlan, pitrou, r.david.murray, theller, vinay.sajip |
| Date | 2009-09-21.21:02:35 |
| SpamBayes Score | 6.5747254e-06 |
| Marked as misclassified | No |
| Message-id | <1253566957.11.0.0207988326745.issue6958@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009-09-21 21:02:37 | exarkun | set | recipients: + exarkun, theller, georg.brandl, vinay.sajip, ncoghlan, pitrou, eric.smith, doughellmann, r.david.murray, michael.foord |
| 2009-09-21 21:02:37 | exarkun | set | messageid: <1253566957.11.0.0207988326745.issue6958@psf.upfronthosting.co.za> |
| 2009-09-21 21:02:35 | exarkun | link | issue6958 messages |
| 2009-09-21 21:02:35 | exarkun | create | |