-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Doc and cosmetics #1395
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
Doc and cosmetics #1395
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice PR, thanks for it. I'm just not sure why was f017eb9 sneaked in?
Also can we update the tox.ini
to reflect the styles you fixed?
@@ -410,7 +410,7 @@ def make_package(args): | |||
|
|||
def parse_args(args=None): | |||
global BLACKLIST_PATTERNS, WHITELIST_PATTERNS, PYTHON | |||
default_android_api = 12 | |||
default_android_api = 19 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this change in this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because I branched off the set_app_platform_19 branch. Will remove before I ask for a review.
@@ -5,3 +5,4 @@ | |||
|
|||
# APP_ABI := armeabi armeabi-v7a x86 | |||
APP_ABI := $(ARCH) | |||
APP_PLATFORM := android-19 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, I don't think that change should be part of a "cosmetic changes" PR. What do you guys think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, this should not be added at all without an actual framework around what its value should be and how the user should control it. Setting it to a fixed value will work in some circumstances, but break others.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pr was labeled a WIP because it's a work in progress. It's this not a known protocol? Not ready to be merged because i am aware of these issues. When it's ready i will remove that WIP prefix :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep I missed that one, cheers 👍
c27a6bf
to
df428cb
Compare
@inclement, @AndreMiras |
Thanks @Zen-CODE yes I was asking for tox, but I wasn't sure if you fixed per error cross project or just per file. So indeed he would complain and we can leave it as it is then. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, thanks!
Could you please wait for green build before merging? To be sure to be sure
Although there are many changes here, they are all cosmetic and should not affect any behavior. I know it's not painful to make large and sweeping changes unnecessarily, but I think these are important for readability + pep8 compliance.
The types of changes and rationale are outlines below: