The tests are no longer run on travis, but in a docker, developer machines or a windows vm.
The code was essentially dead for months now. Fix that by explicitly passing in --ci to the test runner on our docker and appveyor windows vm.
The tests are no longer run on travis, but in a docker, developer machines or a windows vm.
The code was essentially dead for months now. Fix that by explicitly passing in --ci to the test runner on our docker and appveyor windows vm.
makes sense — concept ACK
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
No conflicts as of last run.
Concept ACK.
Why so many style-only changes in the same commit?
Passing the value through touches a lot of function signatures and I run a python formatter on all changes I make before submitting a pull request. In the hope that no one can complain about my code style...
$ which yfd
alias yfd='PATH=/home/marco/workspace/yapf-diff/virt_env_3_yapf/bin python3 /home/marco/workspace/yapf-diff/yapf-diff.py -p1 -i'
A lot of it seems like your personal preference for style, and it inflates the diff substantially. For example, I don't think there's project guidelines about whether continuation lines of long function calls should be aligned to the opening parens or to some other indentation (both are fine under PEP8 https://www.python.org/dev/peps/pep-0008/#indentation).
This seems like a +-5 line diff without the style changes. At the least, can you split the style changes into a separate commit so it's obvious what reviewers are supposed to be paying attention to?
Removed the style change that affected lines that were in proximity to actually changed lines.
utACK fa43626611f4a76cbc361ea89e4989f80d2fa7d7
utACK fa43626611f4a76cbc361ea89e4989f80d2fa7d7