[tahoe-lafs-trac-stream] [tahoe-lafs] #2138: file formatting conventions for text files in our source repo

[tahoe-lafs]

#2138: file formatting conventions for text files in our source repo
-----------------------------+-------------------------------------
     Reporter:  zooko        |      Owner:  daira
         Type:  enhancement  |     Status:  new
     Priority:  normal       |  Milestone:  undecided
    Component:  unknown      |    Version:  1.10.0
   Resolution:               |   Keywords:  review-needed docs easy
Launchpad Bug:               |
-----------------------------+-------------------------------------

Comment (by daira):

 I don't agree that the fill column for Python code should be 77. It's
 unnecessary short and not consistent with the line wrapping in the
 majority of our existing code. [wiki:CodingStandards] says:

 > Ignore the part of PEP-8 which specifes 79- or 72- char line widths.
 Lines should preferably be less than 100 columns, but we don't enforce
 this strictly. It is more important to break lines at points that are
 natural for readability than to follow a fixed line width restriction.
 Where possible, continuation lines should be indented as far as necessary
 to make them match up with the subexpression (e.g. argument list) they
 belong to.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2138#comment:6>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage