[Bug 809951] Re: assumes untagged extensions are built for Python 3.1

Scott Kitterman ubuntu at kitterman.com
Sun Jan 22 17:41:59 UTC 2012


This is fixed in precise and oneiric.

** Changed in: python3-defaults (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python3-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/809951

Title:
  assumes untagged extensions are built for Python 3.1

Status in “python3-defaults” package in Ubuntu:
  Fix Released

Bug description:
  I'm currently packaging python3-gobject, and it took me a while to see
  why python3 doesn't want to find the built extensions. Turns out that
  dh_python3 did

  W: dh_python3:231: renaming _gobject.so to _gobject.cpython-31mu.so
  W: dh_python3:231: renaming _gi.so to _gi.cpython-31mu.so
  W: dh_python3:231: renaming _glib.so to _glib.cpython-31mu.so

  but as I was building with 3.2 only (py3versions --supported
  --version) python looked for _gobject.cpython-32mu.so.

  This is apparently a bug in the upstream build system which doesn't
  produce tagged libraries in the first place. I'm going to fix that.

  However, Barry said that dh_python3 should not assume that untagged
  libraries are for 3.1. I guess it should rather fail to build, or at
  least offer an option to explicitly specify which version the
  libraries are built for? (That gets impractical once we build for more
  than one version, though).

  Upstream installs the files as "_glib.so"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/809951/+subscriptions




More information about the foundations-bugs mailing list