pylint in PyScript doesn't work if pylint is installed as egg

[GoogleCodeExporter]

What steps will reproduce the problem?
1. install pylint with easy_install
2. start PyScripter and write a helloworld script
3. run pylint from 'Tool' -> 'Tools' -> 'pylint'

What is the expected output? What do you see instead?
Expected result: pylint will run successfully with result
Actuan result: pylint fails to run because of pylint installation path. Error: 
C:\Python26\python.exe: can't open file 
'C:\Python26\Lib\site-packages\pylint\lint.py': [Errno 2] No such file or 
directory. Process "Pylint" terminated, ExitCode: 00000002

PyScript expect pylint path: C:\Python26\Lib\site-packages\pylint\lint.py
But the actual installatino path: 
C:\Python26\Lib\site-packages\pylint-0.21.3-py2.6.egg\pylint

Please use labels and text to provide additional information.
pylint

Original issue reported on code.google.com by xue...@gmail.com on 21 Oct 2010 at 6:22

[GoogleCodeExporter]

The tools are fully configurable and are there as examples of what can be done.

Go to Tools, Configure Tools and edit the pylint parameters to something like
$[PythonDir-Short]Lib\site-packages\pylint-0.21.3-py2.7.egg\pylint\lint.py 
$[ActiveDoc-Short] -f parseable

or whatever else makes sense for your python/pylint installation.

Original comment by pyscripter on 21 Oct 2010 at 12:33

• Changed state: As-Designed

[GoogleCodeExporter]

This message also appears when PyLint is not installed.

I thought that PyLint was integrated into PyScripter, or at least installed 
with it.

At the very least, a helpful error message instead of the cryptic "Process 
"PyLint" terminated, ExitCode: 00000002" would be useful.

Original comment by iainel...@hotmail.co.uk on 30 Mar 2011 at 11:40

[GoogleCodeExporter]

The infrastructure (External Tools) for having external processes interacting 
with PyScripter is quite generic.  PyScripter uses this infrastructure to 
exploit PyLint.  The message you saw is what you get if you run the Pyling 
command in a command prompt.

All the tools under Tools, Tools use such infrastructure. They can be modified 
and they are highly configurable (Tools, Configure Tools).  See the help topics 
on External Tools and Parameters for further information.

Original comment by pyscripter on 29 May 2011 at 1:17

[GoogleCodeExporter]

This documentation is completely inadequate for a tool as complicated as 
pylint, which also has inadequate documentation.  Are we supposed to run the 
exe version?  the .py version?  What are appopriate arguments and settings?  
Just because you have a dialog box with some edit fields doesn't mean 
Pyscripter is "configurable."

Original comment by lewis_le...@hotmail.com on 15 Mar 2013 at 10:01

[GoogleCodeExporter]

Got it to work by looking at other examples.  REAL documentation would help.  
Basically the application is "python" and the parameters are the command line 
for python.  

But the output just goes to the command output window.  

Is there anyway this output can be captured and displayed in context, as 
plugins for Sublime Text and Komodo do? 

Original comment by lewis_le...@hotmail.com on 15 Mar 2013 at 10:35

[GoogleCodeExporter]

What the heck:

It's not great, but neither is pylint.
In Sublime Text2 I had so many filters that all I got were some suggestions for 
spacing and indentation.  The only truly useful thing was warnings for 
undefined variables, which saves some runtime errors.
There really is not that much reason to have pylint running constantly.  I did 
learn how to make my code cleaner;  now I just do that.
Running occasionally is good enough.
The output is pretty tedious to go through, but most of it can be ignored.
I take it back.
It WOULD be nice if the commands panel was better documented.  It WOULD be 
better to make things work out of the box.  But, pylint doesn't really need 
perfect "realtime" integration.

Original comment by lewis_le...@hotmail.com on 15 Mar 2013 at 10:18