projects / tools / git-buildpackage.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 96360f2) | patch
log: don't automatically setup gbp-specific logger
authorMarkus Lehtonen <markus.lehtonen@linux.intel.com>
Thu, 10 Jul 2014 06:42:35 +0000 (09:42 +0300)
committerMarkus Lehtonen <markus.lehtonen@linux.intel.com>
Fri, 14 Nov 2014 12:22:00 +0000 (14:22 +0200)
commit3b999dad5d8e38059ffdddb61a9ea660ebc94199
treece378bb66cb50d01c6cfbca005765b1cee2ac613tree | snapshot
parent96360f27eaa09388287e2e43ec557e489617fb91commit | diff
log: don't automatically setup gbp-specific logger

This makes it nicer to use gbp.* modules (e.g. gbp.git) in other
software projects which may have their own logging setup. After this
change, just importing gbp.* modules won't forcibly setup gbp-specific
logging. However, gbp logging is initialized whenever the
gbp.log.getLogger function is called which makes logging in existing gbp
commands behave just like before.

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
gbp/log.py diff | blob | history
tests/component/__init__.py diff | blob | history
Domain: SCM / Build;