fix: SyntaxError

[rachmadaniHaryono]

Proposed changes

• resolve SyntaxErrors (Python 3) #43
• file is formattted by darker
• remove unnecessary list addition

Types of changes

Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[blueyed]

Thanks for this.
Haven't looked into it yet, but it seems like a rebase is required to trigger CI correctly!?

[rachmadaniHaryono]

Unfortunately I don't have my computer for a month or 2 so I can't rebase it for now

[mattip]

Maybe closing/reopening will retrigger CI?

[mattip]

CI on travis should probably be disabled, it costs "credits" to run on x86_64

[mattip]

CI is passing, where it can

[blueyed]

Apparently code formatting was also applied, likely using black?
I think only fixing errors might be better / easier to review, but am not opposed to have it as it is now.

[rachmadaniHaryono]

Apparently code formatting was also applied, likely using black?

this one https://github.com/akaihola/darker

I think only fixing errors might be better / easier to review, but am not opposed to have it as it is now.

i dont know style used on this repo so i used darker formatter as default

if there is error due to code style i will remove it from pr and make the minimal change

[blueyed]

Now it appears with "home" only, but likely is also meant for "end". (just from what I think/see, no idea really).
I wanted to ensure that the comment's meaning/location/reference is kept (which was given before due to whitespace alignment), but now it is even less clear.

[jayvdb]

Ya I agree. It looks like the comment spans multiple lines and starts with "the entries in the terminfo database.." IMO it should be on a separate line, before the end & home lines.

[rachmadaniHaryono]

0262f36 fix that

should there be new line between help and comment? if yes, i will create another commit for that

[millerjason]

@blueyed is this ready for merge?

[rachmadaniHaryono]

i think it is ready

some suggestion already added to pr