[code-quality] Namespaced packages and relative imports

2014-05-16 Thread François Vanderkelen
Hi experts ! I am struggling with Pylint with an issue that might be a problem coming from my code. Since I am relatively new to python (~1year) I would like to have your input on the matter. I am trying to split a big python project I am doing for my company into several packages, allowing me to

Re: [code-quality] Namespaced packages and relative imports

2014-05-16 Thread Sylvain Thénault
On 16 mai 11:16, François Vanderkelen wrote: > Hi experts ! Hi François, > I am struggling with Pylint with an issue that might be a problem coming > from my code. Since I am relatively new to python (~1year) I would like to > have your input on the matter. > > I am trying to split a big python

Re: [code-quality] Namespaced packages and relative imports

2014-05-16 Thread François Vanderkelen
Hi Sylvain, First of all thanks for the quick answer. I tried to create a dummy project (the real one is confidential and not mine to give to the community) and it helped me narrow down my two issues. The ImportError: No module named project is linked to the relative import, and I could not repro

Re: [code-quality] Namespaced packages and relative imports

2014-05-16 Thread Sylvain Thénault
On 16 mai 14:42, François Vanderkelen wrote: > Hi Sylvain, > > First of all thanks for the quick answer. I tried to create a dummy project > (the real one is confidential and not mine to give to the community) and it > helped me narrow down my two issues. > > The ImportError: No module named proj

Re: [code-quality] Namespaced packages and relative imports

2014-05-16 Thread François Vanderkelen
I tried multiple things, first even if I install the package before running pylint it won't work except on one of my machines. So I tried to narrow it down with setuptools : Working with 0.9.8 Not working with 2.2 (ImportError) Not working with 3.6 (ImportError) I guess setuptools changed someth

[code-quality] inference ordering

2014-05-16 Thread George Schneeloch
I've been working on a pylint-brain plugin to do inference based on docstring type information. I'd like to set the order of type inference such that, if there is a type already found it uses that, else it uses what's in the docstring. Is there a way to do this? I'd also like to avoid clobbering ot