Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Introductions and cleanups #419

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Introductions and cleanups #419

wants to merge 6 commits into from

Commits on Jul 27, 2018

  1. Ignore .pyc files in the tree 

    Signed-off-by: Zygmunt Krynicki <[email protected]>
    @zyga
    zyga committed Jul 27, 2018
    Configuration menu
    Copy the full SHA
    f975faf View commit details
    Browse the repository at this point in the history

  2. Use: if foo: ... rather than if(foo): ... 

    The extra parentheses are not required and are not idiomatic python

Signed-off-by: Zygmunt Krynicki <[email protected]>
    @zyga
    zyga committed Jul 27, 2018
    Configuration menu
    Copy the full SHA
    9538233 View commit details
    Browse the repository at this point in the history

  3. Bump Copyright

    @zyga
    zyga committed Jul 27, 2018
    Configuration menu
    Copy the full SHA
    086f24b View commit details
    Browse the repository at this point in the history

  4. Sort imports according to standards 

    The standard import order is stdlib, 3rd party, internal
with newline between each section.

Signed-off-by: Zygmunt Krynicki <[email protected]>
    @zyga
    zyga committed Jul 27, 2018
    Configuration menu
    Copy the full SHA
    4efdf1c View commit details
    Browse the repository at this point in the history

  5. Remove unneeded, empty __init__ 

    Signed-off-by: Zygmunt Krynicki <[email protected]>
    @zyga
    zyga committed Jul 27, 2018
    Configuration menu
    Copy the full SHA
    5c27b9c View commit details
    Browse the repository at this point in the history

  6. Future-import print_function, fix print calls 

    Apart from the future import where print is a function, not a statement, fix
incorrect print formatting calls. Calls like print("%s" % (foo)) are subtly
broken, depending on the value of foo, since (foo) is not a tuple but really
syntactic no-op. The correct way to do that is to use print("%s" % (foo,))

Signed-off-by: Zygmunt Krynicki <[email protected]>
    @zyga
    zyga committed Jul 27, 2018
    Configuration menu
    Copy the full SHA
    b8e4441 View commit details
    Browse the repository at this point in the history