Changes between Version 62 and Version 63 of DeveloperGuidelines/CodeConventions
- Timestamp:
- 01/26/16 12:13:58 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DeveloperGuidelines/CodeConventions
v62 v63 99 99 2) 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. 100 100 101 3) Before indexing, splitting, slicing or iterating over a user-string, we always convert it into a unicode using :101 3) Before indexing, splitting, slicing or iterating over a user-string, we always convert it into a unicode using s3_unicode, e.g.: 102 102 103 103 {{{ … … 105 105 }}} 106 106 107 4) To ensure correct behavior of lower() and upper() conversion, we convert into unicode first, using s3_unicode :107 4) To ensure correct behavior of lower() and upper() conversion, we convert into unicode first, using s3_unicode, e.g.: 108 108 109 109 {{{