I'd could review and check in patches for epydoc compatibility (based on the boost trunk). Ralf
----- Original Message ---- From: Rosen Diankov <rosen.dian...@gmail.com> To: cplusplus-sig@python.org Sent: Mon, July 26, 2010 12:57:09 PM Subject: [C++-sig] docstrings not being interpreted with the correct encoding Hi all, I'm using epydoc to document the Boost.Python-built shared object. Everything has been going great except for one minor issue of epydoc (and probably other documentation tools) not being able to extract the correct docstring encoding (utf-8 in my case). Let A be a class and foo be its member function. Then epydoc uses the "A.foo.im_func.__module__" attribute to get the global module, for which it extracts the encoding the module has set. The problem is that A.foo.im_func is a Boost.Python.function object and does not have any '__module__' attribute. Because epydoc cannot find the __module__ attribute, it cannot get the correct encoding of the docstrings, and non-latin characters are turned into garbage. This is testing with boost python 1.40 thank you, rosen, _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
