mdipierro wrote this on Thu, Feb 05, 2009 at 01:12:07PM -0800. My reply is below.
> 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. > 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. Yes, *PythonTidy* could be much more psychic in the way it wraps long function calls, but I'm not -- apparently. I'm waiting for a snazzy algorithm that divides the separable from the inseparable to drop in my lap. A better solution is to ignore PEP8 (and howls of protest from *emacs* editor users) and specify a longer output line length in *PythonTidy*: > COL_LIMIT = 132 # for example. An even better solution is manually to refactor complex script statements into a series of shorter ones, which is -- I believe -- beyond the scope of *PythonTidy* (but the same is true of all code beautifiers). -- .. Be Seeing You, .. Chuck Rhode, Sheboygan, WI, USA .. Weather: http://LacusVeris.com/WX .. 24° — Wind S 15 mph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
