Bug#526080: please don't call X methods on import

martin f krafft madduck at debian.org
Wed Apr 29 09:16:15 UTC 2009


also sprach Josselin Mouette <joss at debian.org> [2009.04.29.1049 +0200]:
> Why? Does this cause any problems? This is not so uncommon
> practice in Python modules.

It prints warnings and possibly errors for tools that don't even
need X, like jp_*_lookup in the jpilot package, or reportbug. Those
need to import python-gtk2 (or modules importing python-gtk2) for
various reasons, and if only because it's common practice to
unconditionally include modules in Python.

It also causes performance degradation. If I don't use X, why should
I need to "pay" for initialisation of X methods?

-- 
 .''`.   martin f. krafft <madduck at d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20090429/5f311b3e/attachment.pgp>


More information about the pkg-gnome-maintainers mailing list