Changes between Version 17 and Version 18 of CodingStandards


Ignore:
Timestamp:
Aug 27, 2009, 2:19:16 PM (10 years ago)
Author:
flip
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CodingStandards

    v17 v18  
    209209  If you're ever confronted with a choice as to what non-ASCII encoding to
    210210  use, choose utf-8.
    211 
    212   Related note: there are files in PyVespa that have been generated by wxGlade
    213   that contain this Python metacomment:
    214 }}}
    215 {{{
    216 #!python
    217      # -*- coding: iso-8859-15 -*-
    218 }}}
    219 {{{
    220 #!rst
    221   Please change this to comply with PEP 8. In practical terms, this means use
    222   ASCII unless you need non-ASCII characters, in which case use utf-8. It'd be
    223   nice if wxGlade would not output the encoding metacomment at all for ASCII
    224   files, but I don't know if we can control that.
    225211
    226212- Always use / as the path separator. Microsoft operating systems accept both