[web2py:15968] Re: PEP 8 (Style Guide for Python Code) Compliance

2009-02-06 Thread Chuck Rhode
g would be to go over the output from *PythonTidy* to restore some esthetics to more complex sections of the code. Remember: Code beautification is a sometime thing. Doing it repetitively is risky. Doing it excessively is wasteful. Doing it obsessively is crazy. -- .. Be Seeing You, .. Chuck Rhode,

[web2py:15937] Re: PEP 8 (Style Guide for Python Code) Compliance

2009-02-05 Thread Chuck Rhode
      stdout=PIPE, > >                     stderr=PIPE, > >                     shell=True, > >                     close_fds=True, > >                     ) Pick a different value for MAX_SEPS_FUNC_REF in *PythonTidy*. See my reply to achipo, above. -- .. Be Seeing You, .. Chuck

[web2py:15936] Re: PEP 8 (Style Guide for Python Code) Compliance

2009-02-05 Thread Chuck Rhode
7;s relatively easy to comment out the old code, leaving it inactive but in place so it's convenient to restore when testing is complete. -- .. Be Seeing You, .. Chuck Rhode, Sheboygan, WI, USA .. Weather: http://LacusVeris.com/WX .. 17° — Wind SW 3 mph --~--~-~--~~~-

[web2py:15927] Re: PEP 8 (Style Guide for Python Code) Compliance

2009-02-05 Thread Chuck Rhode
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°

[web2py:15925] Re: PEP 8 (Style Guide for Python Code) Compliance

2009-02-05 Thread Chuck Rhode
.. Be Seeing You, .. Chuck Rhode, Sheboygan, WI, USA .. Weather: http://LacusVeris.com/WX .. 24° — Wind S 20 mph --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this g

[web2py:15909] Re: PEP 8 (Style Guide for Python Code) Compliance

2009-02-05 Thread Chuck Rhode
mdipierro wrote this on Wed, Feb 04, 2009 at 09:30:06AM -0800. My reply is below. > look into gluon/compileapp.py Sorry, I couldn't *unzip* your archive with version 5.52-9etch1, which is included in Debian. -- .. Be Seeing You, .. Chuck Rhode, Sheboygan, WI, USA .. Weathe

[web2py:15869] Re: PEP 8 (Style Guide for Python Code) Compliance

2009-02-04 Thread Chuck Rhode
n do string substitution in the *eval* statement. *PythonTidy* doesn't see the arguments as code in their own right, so it shouldn't interfere with them; nevertheless, IIRC, use of *eval* is one of the perverse reasons that some Python test-suite examples can't be tidied up.

[web2py:15866] Re: PEP 8 (Style Guide for Python Code) Compliance

2009-02-04 Thread Chuck Rhode
On Feb 3, 11:44 am, mdipierro wrote: > Thank you chuck for pythontidy and glad to have you on board. Do you > want to be in change of pep8 compliance for web2py? Heh! PEP8 compliance is overrated. :-) Thanks, anyway. --~--~-~--~~~---~--~~ You received this mes

[web2py:15815] Re: PEP 8 (Style Guide for Python Code) Compliance

2009-02-03 Thread Chuck Rhode
On Feb 3, 4:08 am, Markus Gritsch wrote: > Now, now. I did not know PythonTidy before, but to be fair one has to > admit, that it does a remarkable job. Thank you for your kind words. I noticed a link to this discussion in the Web-access log for my site. I am not familiar with *web2py*, but