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

Use auto-force if a single file argument is being passed #35

Merged
merged 1 commit into from
Jun 3, 2015

Conversation

blueyed
Copy link
Contributor

@blueyed blueyed commented May 4, 2015

This allows checking files that do not end in .py, but are Python
files, e.g. through a shebang line.

Additionally or instead the allow function could look for a shebang line like #!/usr/bin/env python, but would then have to open the file, which is bad when running it against a directory.

I think that passing a single path to a file should automatically check it.

This allows checking files that do not end in `.py`, but are Python
files, e.g. through a shebang line.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 79.74% when pulling 71a9fb5 on blueyed:auto-force-with-one-arg into 04ffdbc on klen:develop.

@blueyed
Copy link
Contributor Author

blueyed commented May 6, 2015

@klen
The build failures appear to be unrelated?!

Anyway, is this going to fly like that?

klen added a commit that referenced this pull request Jun 3, 2015
Use auto-force if a single file argument is being passed
@klen klen merged commit 0d18284 into klen:develop Jun 3, 2015
@klen
Copy link
Owner

klen commented Jun 3, 2015

Sorry for the late response and thank you.

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

Successfully merging this pull request may close these issues.

None yet

3 participants