On 04/25/2014 05:42 PM, Donald Stufft wrote: > On Apr 25, 2014, at 7:20 PM, Ethan Furman wrote: >> On 04/25/2014 03:26 PM, Donald Stufft wrote: >>> >>> pep8.py doesn’t violate PEP8, it just takes a stricter view of it. >> >> If pep8 reports errors on things that PEP 8 says are okay, that's a violation. > > Being stricter is not a violation, it’s being stricter. Then it should be called stricterThanPep8. ;) I think we're going to have to agree to disagree on this point. A tool that implements PEP 8 [1], but tells me that something PEP 8 allows is an error -- well, that's not PEP 8 then, is it? At any rate, this part of the thread is pretty off-topic, so this is my last post about it. -- ~Ethan~ [1] Yes, I checked the site for pep8, and saw the escape clause of "some of the style conventions" -- the problem is the cognitive dissonance between the name of the tool and the actions of the tool.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4