Hi, On 13 August 04:02, Gelonida N wrote: > After a certain number of files I get error messages about 'too many > open file handles' several people have reported this pb, generally using windows. This is probably due to addition of .file_stream attribute on module nodes. This should probably be handled differently so that:
* only module that will be analyzed by pylint have this attribute (this is not needed when module is only used for proper inference) * pylint should drop/close it once processing of a module is over > I will investigate further whenever I have time again to look at this issue. > Currently I fell back to run one pylint process for each file, which is > hooribly slow (~40 minutes) but working as I have to finish some other > tasks urgently and as the run time is not the biggest problem at the moment. PyLint has not built its reputation by being quick ;) > What I wanted to know in general is following: > Does pylint 'only' analyze all files or does it really import the code > to be analyzed? pylint doesn't actually import code (beside C-compiled module, as this is the only way to get a clue about what's inside) > The reason why I'm asking is, is whether I should look out for commands, > which are not protected with > > if __name__ == '__main__': statements > (This might be one reason for too many open file handles) As I said above, this is probably not the problem. -- 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
