On 10 novembre 12:50, Naty Bidart wrote:
> Hello list!
Hi,
> We're heavily using pylint in most of the Ubuntu One projects at
> Canonical, and I'm very happy with it.
nice to hear :)
> Ubuntu One is implemented by several in independent projects, but
> all of them provide the ubuntuone python package.
>
> So, for example, we have ubuntuone.controlpanel and
> ubuntuone.devtools. Those two are separated projects, where each
> source tree looks like this:
>
> ubuntuone/
> __init__.py
> devtools/
> __init__.py
> ....
>
> ubuntuone/
> __init__.py
> controlpanel/
> __init__.py
> ....
>
> and in both ubuntuone/__init__.py we have the exact same content:
>
> __import__('pkg_resources').declare_namespace(__name__)
The pb is that pylint doesn't understand that yet... Nor direct __path__
manipulation.
I think you can get it working by using --init-hook option to get
ubuntuone package imported so its path is properly set, eg:
pylint --init-hook="import ubuntuone" ...
or something similar.
--
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
[email protected]
http://lists.logilab.org/mailman/listinfo/python-projects
