This bug was fixed in the package pygobject - 3.12.0-1ubuntu1
---
pygobject (3.12.0-1ubuntu1) trusty-proposed; urgency=medium
* Add 00upstream-importerror-logging.patch: Raise ImportError when importing
modules not found in repository, instead of logging to stderr. The former
Hi Adam, sorry for the delay.
Installing python3-gi (and python3-gi-cairo) version 3.12.0-1ubuntu1
fixed the issue for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
Hello Christopher, or anyone else affected,
Accepted pygobject into trusty-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/pygobject/3.12.0-1ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Trusty fix uploaded to SRU review queue.
** Description changed:
When failing to import a module the gi.repository import.py module logs an
error with `logging.error(..)` causing a logging handler to be added.
This basically breaks the ability to configure the logging as it happens so
early
** Summary changed:
- Failing to import module adds noise to the logging stream
+ Failing to import module breaks logging configurability and adds noise
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.la
5 matches
Mail list logo
