Closed mjschultz closed 9 years ago
I decided to drop Python 3.2 tests since this is a fairly unicode-aware app and Python 3.2 dropped support of the u'unicode'
literal notation. This was quickly realized to be a bad idea and was added back in Python 3.3 and 3.4 to make it easier to port projects like this.
I can attempt to jump through the hoops to get Python 3.2 support but I think it would make the code much more convoluted than it needs to be.
I would not mind a PyPI release if you merge this! :)
Repository health increased by 0.08% when pulling 808eaa1 on mjschultz:python3 into fb7ac2a on tarak:master.
Thx! Sorry for the delay...
This does a few small changes to add support and testing for Python 3:
.travis.yml
to test Python3.2, 3.3, and 3.4 in addition to 2.6 and 2.7Within the code I've changed instances of
force_unicode
toforce_text
andsmart_unicode
tosmart_text
; see Django's guide to Porting to Python 3 for details.I also instrumented some code to handle the "
xrange
is justrange
in Python 3" problem soxrange
is used in Python 2 andrange
is used in Python 3.