On Wed, Nov 26, 2014 at 7:39 AM, Skip Montanaro
wrote:
> Let me see if fixing that solves the problem. My guess is that it will.
That was it! Thanks for the excellent hint, Marius.
Skip
___
code-quality mailing list
code-quality@python.org
https://ma
On Wed, Nov 26, 2014 at 4:02 AM, Marius Gedminas wrote:
> What's in the #! line of /opt/local/bin/pylint?
Ack! I'll bet that's the problem. Our production Python
(/opt/local/bin/python) was compiled without debug symbols. Desperate at
one point to step through the interpreter's C code, I built
On Tue, Nov 25, 2014 at 02:54:03PM -0600, Skip Montanaro wrote:
> We have a rather peculiar software distribution system here at work. I
> downloaded, packaged, and installed astroid, logilab-common, and pylint.
> When I run pylint now (1.1.0 worked just fine), I get this error:
>
> Traceback (mos
I had a similar issue and the problem was that somehow I had two setuptools
versions installed... and the older version was overwriting the new...
Hope that helps
--
Joaquin Sargiotto
El nov 25, 2014 5:54 p.m., "Skip Montanaro"
escribió:
> We have a rather peculiar software distribution system h
We have a rather peculiar software distribution system here at work. I
downloaded, packaged, and installed astroid, logilab-common, and pylint.
When I run pylint now (1.1.0 worked just fine), I get this error:
Traceback (most recent call last):
File "/opt/local/bin/pylint", line 6, in
from
