On 08/12/2011 12:06 AM, Derek Harland wrote: > On 11/08/2011, at 23:30 , Gelonida N wrote: > >> On 08/11/2011 12:43 PM, Derek Harland wrote: >>> On 11/08/2011, at 19:49 , Gelonida N wrote: >> >>>> ... >>>> Additionally it might have helped of course if the official web site >>>> (being marked as updated 8th of August 2011) had not mentioned a command >>>> (pylint.lint.run_py), that I couldn't find >>> >>> If you grep the source you'll see that py_run now exists in pylint.epylint. >>> >> >> Derek, Thanks once more. > >> It still might be useful to fix the official document, don't you think so? > > I am not a maintainer on this project. But if I may suggest ... as in all > open-source projects authored by people who give their valuable time freely > and generally have many issues to look at ... if you have found a problem or > there is something you would like fixed then the best thing you could do > would be to provide an actual patch that fixes that problem. > > And in this case the effort required is very small ... the place to start > would be in the doc/ subdirectory of the source. > Generally speaking your advice is good for the current case I'm at a complete loss what you mean.
I mentioned, that I looked at the logilab web site (in particular at http://www.logilab.org/card/pylint_manual#advanced-usage ) and that I found below text. > It is also possible to call Pylint from an other Python program, > thanks to py_run() function in lint module, > assuming Pylint options are stored in pylint_options string, as > > > from pylint import lint > lint.py_run( pylint_options) > > > To silently run Pylint on a module_name.py module, > and get its standart output and error: > > > from pylint import lint > (pylint_stdout, pylint_stderr) = lint.py_run( 'module_name.py', True) I failed with above instructions and was at the time still struggling to find a complete solution (still issues with redirecting the output) additionally grep -R 'grep -R 'To silently run Pylint' $MY_VIRTUALENVDIR returns only one match, which is in epylint.py The documentation is however true for epylint so there is nothing to fix. Downloading the html source from ligilab's web. and editing it (not even knowing the correct solution) and sending it back as a patch might be a very small, but useless effort. I'm very close to a working version and will (as I usually do) follow up on my own posts. _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
