[raring] recent versions break python2.7-dbg: undefined symbol: Py_InitModule4_64

The symbol seems to be there for the non-debug variant:

$ nm -D /usr/lib/x86_64-linux-gnu/libpython2.7.so |grep Py_InitModule
000000000010cd50 T Py_InitModule4_64

but not for _d:
$ nm -D /usr/lib/x86_64-linux-gnu/libpython2.7_d.so |grep Py_InitModule
000000000018df84 T Py_InitModule4TraceRefs_64

However, that seems to have been the case for quantal as well for that particular library; maybe the symbol was provided by something else in earlier versions?

this is expected. see modsupport.h for the macros defining this symbol.

OK, so the symbol is expected, but is breaking "import gi" expected as well? What could the "gi" module do wrong that triggers this with the new python2.7?

Adding a pygobject task then, as something is obviously wrong, but I don't know what.

0 (master) martin@donald:~/upstream/pygobject
$ git grep Py_InitModule
gi/_glib/pyglib-python-compat.h: PyObject *module = Py_InitModule(fullpkgname, functions); \
gi/_glib/pyglib-python-compat.h: module = Py_InitModule(modname, symbol##_functions);

This just uses the usual Py_InitModule (http://docs.python.org/2/c-api/allocation.html), nothing else.

yes, the import fails, when you don't have python-gi-dbg installed.

after installing python-gi-dbg, I get:

$ python2.7-dbg -c 'import gi'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 27, in <module>
    from ._gi import _API, Repository
ImportError: /usr/lib/python2.7/dist-packages/gi/_gi_d.so: undefined symbol: Py_InitModule4_64
[18485 refs]

so it looks like the extension is built using the normal version, not the debug version of the interpreter.

This bug was fixed in the package python2.7 - 2.7.3-12ubuntu5

---------------
python2.7 (2.7.3-12ubuntu5) raring; urgency=low

  * Don't include the _tkinter extension in libpython2.7-dbg.
 -- Matthias Klose <email address hidden> Thu, 20 Dec 2012 14:54:08 +0100

This bug was fixed in the package pygobject - 3.7.3-0ubuntu2

---------------
pygobject (3.7.3-0ubuntu2) raring; urgency=low

  * Rebuild.
  * Re-enable the tests for 2.7-dbg. Closes: #1091615.
 -- Matthias Klose <email address hidden> Thu, 20 Dec 2012 19:13:41 +0100

Thanks Matthias! I just uploaded a rebuild / reenabling tests, and then saw that you already did that:

pygobject (3.7.3-0ubuntu2) raring; urgency=low

  * Rebuild.
  * Re-enable the tests for 2.7-dbg. Closes: #1091615.
 -- Matthias Klose <email address hidden> Thu, 20 Dec 2012 19:13:41 +0100