Hi,
Every time I run pylint, even with just a '--help' arg, the console
window disappears, which (a) makes it inconvenient to use, and (b)
puzzles me. What does a process run from a shell have to do to kill the
console?
I am on WindowsXP, Python 2.6.4, and am running version:
logilab-astng - 0.19.1 -
active
logilab-common - 0.45.2 -
active
pylint - 0.18.1 -
active
...all of which seem to be the latest releases, as reported by yolk -l.
If I redirect to a file, I can see that the expected output (eg. project
analysis or help output) is produced before the process exits and the
console closes.
If I redirect stderr to a file, I see the following output:
F:\Python26\lib\site-packages\pylint\lint.py:314: DeprecationWarning:
use
lgc.optik_ext.check_csv
value = check_csv(None, opt_name,
value)
This happens whether I'm in 'Console2' or plain old built-in Windows
Command Prompt.
I tried uninstalling pylint, logilab-common and logilab (using pip
uninstall) and reinstalling using 'pip install pylint'. This did grab
all three packages, but I noticed it got an old version of
logilab-common (0.44). I still saw the same crash using this too. I
upgraded to 0.45.2 and still see it now.
I'm not in a virtualenv. The same thing happens if I uninstall and
reinstall using easy_install.
I've tried Googling for this, and browing the list posts since 0.18 was
released, and browing the active tickets, but with no joy.
Any clues of things I could try? Many thanks,
best regards,
Jonathan
--
Jonathan Hartley Made of meat. http://tartley.com
tart...@tartley.com +44 7737 062 225 twitter/skype: tartley
_______________________________________________
Python-Projects mailing list
Python-Projects@lists.logilab.org
http://lists.logilab.org/mailman/listinfo/python-projects
