Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for linting executable scripts #240

Open
Hawk777 opened this issue Mar 17, 2023 · 0 comments
Open

Support for linting executable scripts #240

Hawk777 opened this issue Mar 17, 2023 · 0 comments

Comments

@Hawk777
Copy link

Hawk777 commented Mar 17, 2023

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)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant