#22350: Django 1.7 migration files do not support Python 3.2
----------------------------------------------+------------------------
Reporter: treyhunner | Owner: nobody
Type: Bug | Status: new
Component: Database layer (models, ORM) | Version: 1.7-beta-1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+------------------------
Steps to reproduce:
1. Run "python manage.py makemigrations appname" on a new app
2. Run "python3.2 manage.py migrate" (with Django installed in python3.2
site-packages)
3. View traceback due to syntax error. Example:
{{{
File "/.../django-email-log/email_log/migrations/0001_initial.py", line
14
(u'id', models.AutoField(verbose_name=u'ID', serialize=False,
auto_created=True, primary_key=True)),
^
SyntaxError: invalid syntax
}}}
The syntax error is due to the use of the u prefix in front of string
literals.
In my opinion, Python 3.2 support is unimportant because Python 3.3 made
so many syntactic improvements. However, Python 3.2 support is currently
noted in the documentation.
--
Ticket URL: <https://code.djangoproject.com/ticket/22350>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.7a66d25e8a438359a882dde1a9e2353f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
