On Feb 17, 1:49 pm, Jean-Michel Pichavant <jeanmic...@sequans.com>
wrote:

> I can't use it though, I'm still using a vintage 2.5 version :-/

That's a shame. I chose 2.6 as a baseline for this package, because I
need it to work on Python 2.x and 3.x with the same code base and
minimal work, and that meant supporting Unicode literals via "from
__future__ import unicode_literals".

I'm stuck on 2.5 with other projects, so I share your pain :-(

Regards,

Vinay Sajip
-- 
http://mail.python.org/mailman/listinfo/python-list

Reply via email to