Hi, On Sun, Jun 22, 2014 at 10:49:09PM +0530, Vasudev Kamath wrote: > > debug lines are long to make it easy to scan source to check such lines > > by grep. Others, you can call me lazy. I keep terminal width > > relatively large like 100. I will happy to fold 80 if they are not > > debug lines. > > I see, I normally keep everything under pep8 in my python project as its > the standard accepted by python community (ofcourse now screen supports > more than 80 column but we still carry baggage from past happily)
I like to keep code within 80 ch/line if it does not interfare with readability of code. I made exception to use up to 100 char/line for regex data. For debug.debug(...) like line, I made exception to keep it in one line. I hope to keep them so. The trankated lines of these parts do not affect program readability. But Some variables like LMAX in upprecase may be changed to __line_max__ etc. I am open for cleaning up such and reformatting in more readable style if I get patch :-) FYI pep-8 has: | Some teams strongly prefer a longer line length. For code maintained | exclusively or primarily by a team that can reach agreement on this | issue, it is okay to increase the nominal line length from 80 to 100 | characters (effectively increasing the maximum length to 99 characters), | provided that comments and docstrings are still wrapped at 72 | characters. Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
