Message87344
| Author |
cavallo71 |
| Recipients |
akitada, cavallo71, christian.heimes, tarek |
| Date |
2009年05月06日.19:03:01 |
| SpamBayes Score |
1.7629049e-05 |
| Marked as misclassified |
No |
| Message-id |
<1241636584.67.0.288721031608.issue3992@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
This patch changes the log.py in order to make use of the logging
infrastructure.
There are few point tough worth of mention.
There're two separate stages when log.py is used:
a) during the python interpreter build (let's call it bootstrap)
b) for every python setup.py cycle
During the bootstrap log.py doesn't seem have access to the logging
module
(at least on the CentOS/Redhat/Suse build systems, but I assume is true
for
other platforms): in this case a fallback minimal logging is in place.
Once the python is in place (eg. installed) it can make use of the true
logging: this happen when python setup.py <cmd> is used to create a
python module.
A python intepreter built with the patch (from the latest python build)
is hosted in:
http://download.opensuse.org/repositories/home:/cavallo71:/python-opt |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年05月06日 19:03:04 | cavallo71 | set | recipients:
+ cavallo71, christian.heimes, tarek, akitada |
| 2009年05月06日 19:03:04 | cavallo71 | set | messageid: <1241636584.67.0.288721031608.issue3992@psf.upfronthosting.co.za> |
| 2009年05月06日 19:03:03 | cavallo71 | link | issue3992 messages |
| 2009年05月06日 19:03:02 | cavallo71 | create |
|