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
Right now whenever I run PyFlake the file is immediately written to the filesystem, the result is that when I'm simply checking the file it automatically writes to the filesystem which (in the case of syntax errors) results in my development server crashing because it auto-reloads on file changes.
If the command has to write for it to work, can it write to a temporary file instead perhaps?
The better solution would be to pipe the data straight towards the flake8 stdin imho, but not sure if that's too easy to integrate into the current script.
The flake8 command at least supports this using the following syntax:
cat some_python_file.py | flake8 -
The text was updated successfully, but these errors were encountered:
Right now whenever I run PyFlake the file is immediately written to the filesystem, the result is that when I'm simply checking the file it automatically writes to the filesystem which (in the case of syntax errors) results in my development server crashing because it auto-reloads on file changes.
If the command has to write for it to work, can it write to a temporary file instead perhaps?
The better solution would be to pipe the data straight towards the flake8 stdin imho, but not sure if that's too easy to integrate into the current script.
The flake8 command at least supports this using the following syntax:
The text was updated successfully, but these errors were encountered: