[issue26030] Use PEP8 in documentation examples

Ezio Melotti added the comment: > I'll slowly review what I see, and provide little patches from > time to time, only when the PEP8 infringement look obvious. Sounds good to me. If you are not sure you can ask on IRC (#python-dev on freenode) or the core-mentorship mailing list. --

[issue26030] Use PEP8 in documentation examples

Ezio Melotti added the comment: Without a list of places that don't follow the PEP8, I'm going to close this. -- resolution: -> not a bug status: open -> pending ___ Python tracker

[issue26030] Use PEP8 in documentation examples

Changes by Berker Peksag : -- stage: needs patch -> resolved ___ Python tracker ___

[issue26030] Use PEP8 in documentation examples

Julien added the comment: I opened this ticket mainly to know the opinions on those modifications, I'll slowly review what I see, and provide little patches from time to time, only when the PEP8 infringement look obvious. I think the most obvious PEP8 infringement ARE to be fixed, typically

[issue26030] Use PEP8 in documentation examples

Changes by Ezio Melotti : -- nosy: +ezio.melotti versions: +Python 3.6 ___ Python tracker ___

[issue26030] Use PEP8 in documentation examples

Martin Panter added the comment: In general I agree with fixing style problems in the documentation, especially if you supply patches :) -- nosy: +martin.panter stage: -> needs patch ___ Python tracker

[issue26030] Use PEP8 in documentation examples

New submission from Julien: Hi, Shouldn't Python use PEP8 in its examples in the documentation ? I found a lot of missing spaces around binary operators, and things like "setup (name = 'PackageName'," (found in the Distributing section, but that's just a single example) which hurt my eyes

[issue26030] Use PEP8 in documentation examples

Raymond Hettinger added the comment: > I found a lot of missing spaces around binary operators Please don't make trivial changes like this. -- nosy: +rhettinger ___ Python tracker