I guessed that I answered to my question myself.

When making the class names in the C-declarations relative to the top-
level
(the package as several subpackages, in which are modules), the
problem seems to disappear...
which likely means a dormant bug in the class declarations on my end.

Sphinx is a great tool.


L.



On Apr 28, 7:19 am, lgautier <[email protected]> wrote:
> Thanks for your quick answer.
> (more below)
>
> On Apr 19, 2:30 pm, Wojtek Walczak <[email protected]> wrote:
>
>
>
> > laurent napisał(a):
>
> > Hello,
>
> > > Being an happy user of Sphinx, I am trying out the recent
> > > inheritance-diagram extension... but I am facing an annoying issue.
> > > There is a PicklingError raised for a C-level defined type that can
> > > otherwise normally be pickled/unpickled.
>
> > > Would anyone have a hint of what could be happening ?
> > ...
> > > PicklingError: Can't pickle <type 'rinterface.SexpVector'>: import of
> > > module rinterface failed
>
> > What about installing rpy? This package provides rinterface module:
>
> >http://rpy.sourceforge.net/
>
> I am developing rpy2, so I do have it installed when trying
> to build the doc. ;-)
>
> > Not sure if this can help, though. I don't have rpy on my system
> > and still inheritance_diagram extension works for me.
>
> The question might then be: do you have it working for C-implemented
> classes defining their pickling/unpickling methods ?
>
> From the error message, it is looking like Sphinx is trying to import
> the
> package rinterface while it should be importing rpy2.rinterface.
>
> L.
>
> > HTH,
> > --
> > Regards,
> > Wojtek Walczak,http://tosh.pl/gminick/
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sphinx-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sphinx-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to