bryukh / pep8online Goto Github PK

The recommended method changed and it is not recommend to break before the operator instead of after. Both are permissible as long as it is consistent throughout.

# No: operators sit far away from their operands
income = (gross_wages +
          taxable_interest +
          (dividends - qualified_dividends) -
          ira_deduction -
          student_loan_interest)

# Yes: easy to match operators with operands
income = (gross_wages
          + taxable_interest
          + (dividends - qualified_dividends)
          - ira_deduction
          - student_loan_interest)

From Billy Wayne McCann

"""
Could there be an option to download the file once all corrections have been made? That be an excellent feature.
"""

pep8online.com is down

From Abid K.
"""
what about printing the errors in the same window as the code, just against the line of error ? So people can easily compare the code and error. It would be much more productive.
"""

""'
When I first ran the checker, I had at least a page worth of things to fix. Therefore, I had to scroll from the top of the list of Check Results to the Code box and keep on scrolling down like this as long as the list of results was more than a page.

So, I thought I would try another approach: I would fix the Check Results items at the end of the Check Results list first, so I could keep the Code and the last few Check Results in view at the same time. I scrolled to the end of my code to edit it.

When I made my first fix then did a check again (to remove the last item from the results), the code window had reset so that the beginning of the code was in the code window. Therefore, to return to the end of the code, I needed to scroll down to the end again.

Some people (those with fewer results to fix) may prefer to work on the code at the beginning of their program and others (with more to fix) may want to work from the end, so maybe this would work for most people: after the Check button is clicked, then the code could remain in the same position in the code window. This way, wherever the user had been editing, that would still be visible.
"""

From Eric
"""
I have an idea, could you split up real failures from minor failures? For example, I have many lines longer than 79 characters, and don’t care to abide by that rule, but seeing so many errors hides the true issues within the file. By filtering out the trivial things, I can spot the two or three real issues in the document without having to hunt.
"""

From Luke Lee

"""
I really like your PEP8 site. A friend and I wrote something similar to this a few years back for the Django Dash. It allows users to insert a git repo for PEP8 compliance. We would then clone the repo, run PEP8 on it, etc.

The code is here, https://github.com/durden/spygit. It's a bit messy since it was written in a hurry for the 48 hour contest. However, maybe there are some ideas/code you could use?

You can see a 'working' version of that app here, http://spygit.durden.webfactional.com. You site seems much cleaner, but I thought maybe there were some ideas worth taking from this project and combining into yours.

Anyway, nice job on the site. Looking forward to seeing how it evolves.
"""

from Dalba
"""
Also it would have been great if your
tool could be integrated with autopep8[1] so that it could fix common
formatting issues.
"""

According to PEP 8:
Names to Avoid
Never use the characters 'l' (lowercase letter el), 'O' (uppercase letter oh), or 'I' (uppercase letter eye) as single character variable names.

In some fonts, these characters are indistinguishable from the numerals one and zero. When tempted to use 'l', use 'L' instead.

I put the following
l = 20
I = 40
O = 30
into the online checker, and it doesn't recognize it as invalid

From Sunny

"""
But recently there’s a weird thing happened when I pasted the code to the website. There’s always a long distance between the last character in the code and the cursor(the longer your code, the bigger the distance). I guess this has something to do to with the indent value, but I checked the setting on my laptop, it’s normal. By the way, this problem only occurs on my mac Safari browser. I tried it on Google Chrom, it works well.
"""

from Ivan

"""
Было бы здорово если pep8online смог помнить последние код который был вставлен.
Удобная функция для тех кто весь код исправили online закрыли страничку забывая скопировать код.
"""

from dAnjou

"""
make it check code from a URL
"""

from Christian

"""
It would be really cool to have this integrated into TravisCI like coveralls
"""

Because, why not? It's free with certbot/let'sencrypt!

From Stephan

"""
It would be good if you site had a link to PEP 8. At least I can't find one right now.
"""