[Python-Dev] pep8 reasoning
Donald Stufft
donald at stufft.io
Sat Apr 26 02:42:02 CEST 2014
More information about the Python-Dev mailing list
Sat Apr 26 02:42:02 CEST 2014
- Previous message: [Python-Dev] pep8 reasoning
- Next message: [Python-Dev] pep8 reasoning
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Apr 25, 2014, at 7:20 PM, Ethan Furman <ethan at stoneleaf.us> 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. > > -- > ~Ethan~ > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/donald%40stufft.io Not really, any code that passes the pep8.py check is perfectly valid in the eyes of PEP8, if a check was implemented to say, require camelCase method names, then that would be a violation of a check. Being stricter is not a violation, it’s being stricter. ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://mail.python.org/pipermail/python-dev/attachments/20140425/dd7f5f2c/attachment.sig>
- Previous message: [Python-Dev] pep8 reasoning
- Next message: [Python-Dev] pep8 reasoning
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list