Perform unicode migration for reviewboard/scmtools

Review Request #4968 — Created Nov. 15, 2013 and submitted

Information

Review Board
master

Reviewers

Perform unicode migration for reviewboard/scmtools

This change represents an audit of all of our string literals to make sure that
bytestrings are annotated with a leading 'b', and then adds
"from __future__ import unicode_literals" to the beginning of every non-empty
file.

This also includes some changes to use six.text_type for python 2/3
compatibility, marking some additional strings for translation, and changes
some file opens to use 'with'.

Ran unit tests.

Description From Last Updated

Swap these.

chipx86chipx86

Why is six.text_type needed here? Surely _() is sufficient?

chipx86chipx86
david
chipx86
  1. 
      
  2. reviewboard/scmtools/core.py (Diff revision 1)
     
     
     
    Show all issues

    Swap these.

  3. reviewboard/scmtools/git.py (Diff revision 1)
     
     
    Show all issues

    Why is six.text_type needed here? Surely _() is sufficient?

    1. _() returns a functional.__proxy__ object, which can be coerced to unicode, but this particular code path didn't do that coersion, opting instead to raise a ValueError.

  4. 
      
david
chipx86
  1. Ship It!
  2. 
      
david
Review request changed

Status: Closed (submitted)

Change Summary:

Pushed to master (cc82e59)
Loading...