I ever followed pep8 because I too have my own readability standards. nevertheless some people complained so much about the code not being pep8 compliant that I changed it.
Aesthetic issues are subjective. Massimo On Feb 5, 3:00 pm, achipa <attila.cs...@gmail.com> wrote: > After merging in 1.56 with pep8 compliance I must admit I'm less > thrilled than I was initially :( As for whitespace within single > lines, it's ok and welcome, but when it comes to splitting lines, in > some cases it's just terrible. I'm all for standards but I can't > believe the line width enforcement, it just destroys readability. > > Markus Gritsch wrote: > > Hi, > > > IMO web2py should follow the python style guide [1] at least in the > > example code snippets and in the generated scaffolding code. Ideally > > in the gluon sources too. > > > In particular for Python code it looks quite uncommon to omit the > > space after a colon and to have no spaces around operators. e.g. > > > r=f(a,b,c)+g(d,e) > > > should read > > > r = f(a, b, c) + g(d, e) > > > PEP 8 is quite explicit about this in the "Whitespace in Expressions > > and Statements" section. > > > [1]http://www.python.org/dev/peps/pep-0008/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
