[issue2747] Documentation of new gobject types fails

2008-09-12 Thread Georg Brandl
Georg Brandl [EMAIL PROTECTED] added the comment: This turns out to be caused by the same problem that caused the SQLAlchemy model failure: the module was imported twice by autodoc. Should now be fixed in trunk and 0.4.x branch. -- resolution: - fixed status: open - closed

[issue2747] Documentation of new gobject types fails

2008-08-24 Thread Neal Norwitz
Changes by Neal Norwitz [EMAIL PROTECTED]: -- type: crash - behavior ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2747 ___ ___ Python-bugs-list

[issue2747] Documentation of new gobject types fails

2008-05-03 Thread Ali Afshar
New submission from Ali Afshar [EMAIL PROTECTED]: When using the automodule directive on a module that creates new Gobject types (eg custom PyGTK widget), the implicit registration of the imported types fail. (Normally any GObject subclass which has a __gtype_name__ attribute is automatically

[issue2747] Documentation of new gobject types fails

2008-05-03 Thread Ali Afshar
Ali Afshar [EMAIL PROTECTED] added the comment: I have managed to reduce the bug to a tiuny test case. It seems that this only happens when calling automodule directive on a package, with code in __init__.py which registers a new GType. Moving the code to a a regular module inside a package