Skip to content
This repository has been archived by the owner on May 28, 2022. It is now read-only.

Converting to Python 3 #693

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

Converting to Python 3 #693

wants to merge 2 commits into from

Conversation

sunn-e
Copy link
Member

@sunn-e sunn-e commented Oct 9, 2019

Using 2to3.
Creating .bak for backups
Let me know if there are any errors. I am reviewing this currently.

Using 2to3.
Creating .bak for backups
@pep8speaks
Copy link

pep8speaks commented Oct 9, 2019

Hello @sunn-e! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

Line 244:30: E128 continuation line under-indented for visual indent
Line 245:30: E128 continuation line under-indented for visual indent
Line 246:30: E128 continuation line under-indented for visual indent
Line 247:30: E128 continuation line under-indented for visual indent
Line 248:30: E128 continuation line under-indented for visual indent
Line 249:30: E128 continuation line under-indented for visual indent
Line 250:30: E128 continuation line under-indented for visual indent
Line 251:30: E128 continuation line under-indented for visual indent
Line 268:13: E128 continuation line under-indented for visual indent

Line 62:80: E501 line too long (99 > 79 characters)
Line 64:80: E501 line too long (88 > 79 characters)

Line 80:80: E501 line too long (80 > 79 characters)
Line 110:80: E501 line too long (96 > 79 characters)
Line 158:80: E501 line too long (85 > 79 characters)
Line 254:80: E501 line too long (91 > 79 characters)

Line 228:80: E501 line too long (124 > 79 characters)
Line 240:80: E501 line too long (110 > 79 characters)
Line 499:80: E501 line too long (126 > 79 characters)
Line 505:80: E501 line too long (139 > 79 characters)
Line 564:80: E501 line too long (126 > 79 characters)
Line 570:80: E501 line too long (139 > 79 characters)

Line 141:80: E501 line too long (81 > 79 characters)
Line 147:80: E501 line too long (95 > 79 characters)
Line 148:80: E501 line too long (91 > 79 characters)
Line 149:80: E501 line too long (92 > 79 characters)
Line 150:80: E501 line too long (87 > 79 characters)

Line 77:80: E501 line too long (104 > 79 characters)

Line 238:80: E501 line too long (92 > 79 characters)
Line 366:80: E501 line too long (96 > 79 characters)
Line 412:80: E501 line too long (92 > 79 characters)
Line 583:80: E501 line too long (99 > 79 characters)

Line 167:80: E501 line too long (81 > 79 characters)
Line 168:80: E501 line too long (85 > 79 characters)
Line 171:80: E501 line too long (81 > 79 characters)
Line 172:80: E501 line too long (80 > 79 characters)

Line 407:80: E501 line too long (81 > 79 characters)

Line 54:80: E501 line too long (94 > 79 characters)
Line 56:80: E501 line too long (90 > 79 characters)
Line 58:80: E501 line too long (109 > 79 characters)
Line 109:80: E501 line too long (85 > 79 characters)

Line 44:1: E402 module level import not at top of file

Line 47:1: E402 module level import not at top of file

Line 46:1: E402 module level import not at top of file

Line 44:1: E402 module level import not at top of file

Line 62:80: E501 line too long (89 > 79 characters)
Line 66:80: E501 line too long (91 > 79 characters)

Line 45:1: E402 module level import not at top of file

Line 45:1: E402 module level import not at top of file

Line 46:1: E402 module level import not at top of file

Line 45:1: E402 module level import not at top of file

Line 49:1: E402 module level import not at top of file

Line 48:1: E402 module level import not at top of file

Line 47:1: E402 module level import not at top of file

Line 45:1: E402 module level import not at top of file

Line 45:1: E402 module level import not at top of file

Line 47:1: E402 module level import not at top of file

Line 94:80: E501 line too long (87 > 79 characters)

Line 72:80: E501 line too long (87 > 79 characters)
Line 73:80: E501 line too long (87 > 79 characters)
Line 74:80: E501 line too long (84 > 79 characters)
Line 75:80: E501 line too long (81 > 79 characters)

Comment last updated at 2019-10-10 07:28:45 UTC

@zxiiro
Copy link
Member

zxiiro commented Oct 9, 2019

The entire point of Git is that it tracks the history of file changes. Creating .bak files is unnecessary and adds noise to a code review.

You can always grab a previous version of the files by git checkout <commit> or if you tag a point for reference you can always get back to that tag.

Copy link
Member

@zxiiro zxiiro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove all the .bak files. Git's purpose is to track changes to files so backing up files is an entirely pointless in a PR.

@sunn-e
Copy link
Member Author

sunn-e commented Oct 10, 2019

Okay @zxiiro . I will do the changes.

@sunn-e sunn-e requested a review from zxiiro October 10, 2019 07:31
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants