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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: pygobject (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1333512 Title: Failing to import module breaks logging configurability and adds noise Status in Python bindings for GObject: Fix Released Status in “pygobject” package in Ubuntu: Fix Released Status in “pygobject” source package in Trusty: Fix Committed Status in “pygobject” source package in Utopic: Fix Released Bug description: 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 (i.e. at the import stage before an authors code is executed). To reproduce/Example: Run this script: http://pastebin.ubuntu.com/7698632/ Expected outcome: No output to stdout or stderr and the text "log message" in the file "/tmp/example.log Actual outcome: No log file, and this text output to stderr: ERROR:root:Could not find any typelib for rubbish ERROR:root:log message Upstream fix: https://git.gnome.org/browse/pygobject/commit/?id=ac8b59e Regression potential: - The behaviour of raising ImportError on a nonexisting name does not change, but its text changes. Old: ImportError: cannot import name 'foo' New: ImportError: cannot import name foo, introspection typelib not found It's unlikely, however theoretically possible that a program matches on the precise error message. - It's theoretically possible that a program watches for the logged error message and ignores the ImportError. However, that would be extremely bad design, un-Pythonic and brittle as the logging format/destination can be changed arbitrarily. In summary the regression potential is very low. Ubuntu Version: Description: Ubuntu 14.04 LTS Release: 14.04 Package Version: python3-gi 3.12.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1333512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
