#18269: From __future__ import unicode_literals
-------------------------------------+-------------------------------------
Reporter: claudep | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.3
Component: Python 3 | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
If I understand correctly (far from granted in this area):
- if we only support 3.3+, we can use u"" and b"" for unicode and bytes
(resp.)
- to support 3.2, we have to use "" and b""
This doesn't make a big difference, so I agree with Karen and Carl that we
should support 3.2.
I suppose automatic tools exist to help the conversion?
--
Ticket URL: <https://code.djangoproject.com/ticket/18269#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
