-
-
Notifications
You must be signed in to change notification settings - Fork 309
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
Run flake8 without creating physical files #1698
Comments
your best bet is probably to call duplicate of #140 |
@asottile How can I pass my file content as stdin?
That means that I need to pass just "-" as the path argument, isn't. But If I do it, I got the error: My Python code:
|
I can't see your screen. show your full output -- don't hide anything, don't edit it -- otherwise I can only guess at your problem here's my framework for asking questions if you need some explicit pointers about how to ask a useful, helpful question |
I just asked how can I use flkae8 with stdin, because if you noted this way, you probably know how I can do it. It would be great if you share this knowledge My code:
My output:
|
right so whatever |
Sorry for the stupid question, but what do you mean by using the |
looks like thy already fixed it -- afonasev/flake8-plugin-utils@1e07ff4 you can |
It works, thank you a lot for the help! |
Run flake8 without creating physical files
Hello! Can I use flake8 in a Python project via API? The documentation says: Flake8 3.0.0 presently does not have a public, stable Python API. I would like to run flake8 on a dataset to get code quality violations for each code snippet, but I don't want to create physical files with code since I have millions of code snippets. I currently found that flake8 uses FileChecker but didn't find other checkers, e.g.
InMemoryChecker
. Is it true that my use case is not supported?And if it is true, do I understand correctly that if I implement my own сhecker, this will be enough to solve my problem?
The list of the plugins which I would like to use are:
The text was updated successfully, but these errors were encountered: