Closed manodeep closed 4 years ago
Huh - weird! I would have thought that the #209 would have already accounted for the initial commits on this branch.
Hello @manodeep! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers:
Weird about the commits, maybe because we're "reusing" the same branch as the first PR?
@lgarrison Thanks for fixing up the PR. Since the common.mk
file has to be read in first any replacements, I moved the this_python
substitution back down to after the python validation (i.e., where that section was previously)
Here is an overview of what got changed by this pull request:
Issues
======
+ Solved 1
Complexity decreasing per file
==============================
+ setup.py -3
See the complete overview on Codacy
@lgarrison Is this okay to merge?
(I am thinking of rebasing and merging - rather than the usual squash-merge)
Yes, looks good! Either squash or rebase is fine with me, I don't understand the difference well enough to have a strong opinion!
Still fixing #208