On 15 février 14:05, Hans Sebastian wrote: > > I just filed a bug for the OSError: Too many open files issue. #62295
thanks > >> May I ask why are you using this wrapper instead of calling pylint > >> directly ? > >> > > > > I didn't realize that I can pass in a dir that is a python module and it > > will run all its submodules. In this case I can call pylint directly. I'm > > not sure I can do this for what I am trying to do. My task is basically to > > find all python scripts in the source repository and run pylint on each. Is > > there a better approach to of doing that than the approach above? Thanks > > Sorry, I forgot to mention actually with the approach above I am getting > invalid Fatals "Unable to import" for scripts that import sibling modules or > using relative imports. So I also want to ask how to solve this invalid > "Unable to import" problem. Again thanks for any help. you can give several scripts or directory to analyze on pylint command line. To solve 'unable to import' pb, you should set your python path properly. Though if 'pylint path/to/module.py' is unable to import something while 'python path/to/module.py' run smoothly, there may be a bug in pylint. -- Sylvain Thénault LOGILAB, Paris (France) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
