It appears that recent pylint requires a .py extension to do anything useful.
However, it's generally recognized (outside the perl community) that having a file extension on a script just causes the callable interface to needlessly depend on the interpreter used; it makes it harder to rewrite in a different language, for no benefit other than language vanity. Thanks for the great tool though. I'm using: $ /usr/local/cpython-2.6/bin/pylint --version No config file found, using default configuration pylint 1.2.0, astroid 1.0.0, common 0.61.0 Python 2.6.9 (unknown, Apr 23 2014, 16:37:36) [GCC 4.8.1] $ /usr/local/cpython-3.3/bin/pylint --version No config file found, using default configuration pylint 1.2.0, astroid 1.0.0, common 0.61.0 Python 3.3.3 (default, Apr 23 2014, 17:01:23) [GCC 4.8.1] -- Dan Stromberg
_______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
