Changes between Initial Version and Version 1 of Ticket #2138, comment 7
- Timestamp:
- 2013-12-19T00:50:22Z (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2138, comment 7
initial v1 1 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.1 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 accept the full syntax accepted by emacs. 2 2 3 3 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).