-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unicode literals are a no-no for 3.2-compatibility:
File
/home/travis/virtualenv/python3.2.5/lib/python3.2/site-packages/translationstring-1.2-py3.2.egg/translationstring/__init__.py,
line 239
msgid = u'%s\x04%s' % (context, tstring)
^
On 05 Nov 2014, at 15:57, Tres Seaver tsea...@palladion.com wrote:
Unicode literals are a no-no for 3.2-compatibility:
How important is 3.2 compatibility?
Wichert.
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/05/2014 10:44 AM, Wichert Akkerman wrote:
On 05 Nov 2014, at 15:57, Tres Seaver tsea...@palladion.com
wrote: Unicode literals are a no-no for 3.2-compatibility:
How important is 3.2 compatibility?
We don't ordinarily drop a supported
On 05 Nov 2014, at 17:55, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/05/2014 10:44 AM, Wichert Akkerman wrote:
On 05 Nov 2014, at 15:57, Tres Seaver tsea...@palladion.com
wrote: Unicode literals are a no-no for 3.2-compatibility:
+1
Python 3.2 is not likely to be relevant going forward because conservative
users are anyway still on 2.x.
Malthe
On Wed 5 Nov 2014 at 21:39 Wichert Akkerman wich...@wiggy.net wrote:
On 05 Nov 2014, at 17:55, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
