On 09 mars 13:15, Giovanni Gherdovich wrote: > Hi again, Hi, > after some more investigations, > I noticed that actually pyreverse > get associated classes right in > analysing its own source code:
[snip] > Any gotchas? I think you've spotted it: relative import. IIRC by default pyreverse only display on the diagram classes which are coming from the same package. The pb is probably that due to the relative import (and potentially a bad python path), pyreverse think both classes don't belong to the same package. Are you launching pyreverse from withing the package directory you're asking pyreverse to analyze? Also you should probably use absolute import anyway, pylint should have told you relative import are bad ;) -- Sylvain Thénault LOGILAB, Paris (France) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
