[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:           |     Status:  new
  enhancement            |  Milestone:  undecided
     Priority:  normal   |    Version:  1.10.0
    Component:  unknown  |   Keywords:  review-needed docs easy standards
   Resolution:           |  charset utf-8 bom
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by daira):

 * keywords:  review-needed docs easy => review-needed docs easy standards
     charset utf-8 bom


Comment:

 It's not clear that "-*- coding: utf-8-with-signature-unix; fill-column:
 77 -*-" is a valid Python source encoding declaration according to
 [http://www.python.org/dev/peps/pep-0263/ PEP 263]. I don't know what
 Python actually implements, but the PEP doesn't require it to implement
 the full syntax accepted by emacs.

 On the issue of BOMs, I'm with Brian in not seeing the point in adding
 them, especially for Python source code files that don't actually contain
 any non-ASCII characters (i.e. the vast majority of files in the Tahoe-
 LAFS source). And I do see harm in patches that touch large numbers of
 files, since that can create conflicts with other work in progress
 (granted, only trivial conflicts).

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