Changes between Version 62 and Version 63 of DeveloperGuidelines/CodeConventions


Ignore:
Timestamp:
01/26/16 12:13:58 (6 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/CodeConventions

    v62 v63  
    99992) Where we receive str input, we assume utf-8 encoding. Most common encodings are subsets of utf-8 so that this is the safest assumption we can make.
    100100
    101 3) Before indexing, splitting, slicing or iterating over a user-string, we always convert it into a unicode using:
     1013) Before indexing, splitting, slicing or iterating over a user-string, we always convert it into a unicode using s3_unicode, e.g.:
    102102
    103103{{{
     
    105105}}}
    106106
    107 4) To ensure correct behavior of lower() and upper() conversion, we convert into unicode first, using s3_unicode:
     1074) To ensure correct behavior of lower() and upper() conversion, we convert into unicode first, using s3_unicode, e.g.:
    108108
    109109{{{