[Bug 457688] Re: [SRU, 9.10] libboost-python1.38 issues with __doc__ property in Python >= 2.6.3

Scott Kitterman ubuntu at kitterman.com
Sun Apr 4 22:54:15 BST 2010

Wontfix forLucid since 1.38 has been removed.

** Also affects: boost1.38 (Ubuntu Karmic)
   Importance: Undecided
       Status: New

** Also affects: python-visual (Ubuntu Karmic)
   Importance: Undecided
       Status: New

** Changed in: boost1.38 (Ubuntu Karmic)
       Status: New => Confirmed

** Changed in: boost1.38 (Ubuntu Karmic)
   Importance: Undecided => High

** Changed in: boost1.38 (Ubuntu)
       Status: Confirmed => Won't Fix

[SRU, 9.10] libboost-python1.38 issues with __doc__ property in Python >= 2.6.3
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in Python: New
Status in “boost1.38” package in Ubuntu: Won't Fix
Status in “python-visual” package in Ubuntu: Confirmed
Status in “boost1.38” source package in Karmic: Confirmed
Status in “python-visual” source package in Karmic: New

Bug description:
Python >= 2.6.3 has changed the way the __doc__ property is implemented. Boost.Python 1.38 does not account for this, yet, leading to many errors executing Python code using the Boost implemented bindings.

An example trying to use a sample from python-visual:

guy at mountpaku:/usr/share/doc/python-visual/examples$ python orbit.py
Traceback (most recent call last):
  File "orbit.py", line 1, in <module>
    from visual import *
  File "/usr/lib/python2.6/dist-packages/visual/__init__.py", line 59, in <module>
    import cvisual
AttributeError: 'Boost.Python.StaticProperty' object attribute '__doc__' is read-only

The current SVN version of Boost seems to have resolved that issue already. But the version of Boost in "universe" (1.40) still does not seem compatible with this, as python-visual does not compile with that one. I do not know whether the issue with __doc__ itself has already been resolved in 1.40.

Tests have been undertaken to compile python-visual 5.11 from Karmic with Boost 1.38 as well as 1.40, as well as python-visual 5.12 (from Debian Sid) with Boost 1.38. No attempt has been made, yet, to try this with the current stable release 5.13, which has not been "debianified" as of now.

Many packages rely on a working libboost-python. Especially python-visual as contained in "main" of Karmic is completely unusable this way. Other projects, like Python Ogre, also do not work with the present version of Boost.

Anyway, some/many/most/all Python packages relying on libboost-python will definitely be *broken* in the upcoming Karmic if this bug is not resolved in some way.

See also here:

 * python-visual bug with quite some info in the last comments:

 * Post on Python Ogre and the __doc__ property issue:

 * Discussion of a similar issue from PySide:

ProblemType: Bug
Architecture: i386
Date: Thu Oct 22 10:59:00 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: libboost-python1.38.0 1.38.0-6ubuntu6
 PATH=(custom, user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: boost1.38
Uname: Linux 2.6.31-14-generic i686
XsessionErrors: (polkit-gnome-authentication-agent-1:7182): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

More information about the Ubuntu-sponsors mailing list