We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
future: 0.18.2 python: 3.8.2 OS: MacOS 10.15.4
When I run future with multiple processes, the "RefactoringTool: Refactored" stdout is missing.
future
For example, I created the following file:
# foo.py print 1
When running future with multiple processes, I get the following output:
$ futurize -j4 foo.py RefactoringTool: Skipping optional fixer: idioms RefactoringTool: Skipping optional fixer: ws_comma --- foo.py (original) +++ foo.py (refactored) @@ -1 +1,2 @@ -print 1 +from __future__ import print_function +print(1) RefactoringTool: No files need to be modified.
When running future in one process, I get the following output:
$ futurize foo.py RefactoringTool: Skipping optional fixer: idioms RefactoringTool: Skipping optional fixer: ws_comma RefactoringTool: Refactored foo.py --- foo.py (original) +++ foo.py (refactored) @@ -1 +1,2 @@ -print 1 +from __future__ import print_function +print(1) RefactoringTool: Files that need to be modified: RefactoringTool: foo.py
It seems like futurize -j4 is able to correctly analyze the file, but also doesn't recognize that the file exists.
futurize -j4
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Environment
Issue
When I run
future
with multiple processes, the "RefactoringTool: Refactored" stdout is missing.For example, I created the following file:
When running
future
with multiple processes, I get the following output:When running
future
in one process, I get the following output:It seems like
futurize -j4
is able to correctly analyze the file, but also doesn't recognize that the file exists.The text was updated successfully, but these errors were encountered: