You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #55, you said to lint files that do not end in .py (such as executable scripts with no file extension), to pass --force. According to the changelog, in version 8.1.4, that option went away. In actual fact, passing --force on the command line now fails, but passing force=True to pylama.main.parse_options silently succeeds but has no effect, meaning that non-.py files are silently not linted.
As far as I can tell, with --force gone, there is no longer any sane way to use Pylama to lint a bunch of executable scripts whose filenames do not end in .py. Am I just supposed to call pylama.core.run instead (which is not obviously a public API)? Or am I supposed to call pylama.main.check_paths, but pass in the code parameter and a fake filename ending in .py (which also infects the linter error messages)?
The text was updated successfully, but these errors were encountered:
In #55, you said to lint files that do not end in
.py
(such as executable scripts with no file extension), to pass--force
. According to the changelog, in version 8.1.4, that option went away. In actual fact, passing--force
on the command line now fails, but passingforce=True
topylama.main.parse_options
silently succeeds but has no effect, meaning that non-.py
files are silently not linted.As far as I can tell, with
--force
gone, there is no longer any sane way to use Pylama to lint a bunch of executable scripts whose filenames do not end in.py
. Am I just supposed to callpylama.core.run
instead (which is not obviously a public API)? Or am I supposed to callpylama.main.check_paths
, but pass in thecode
parameter and a fake filename ending in.py
(which also infects the linter error messages)?The text was updated successfully, but these errors were encountered: