Thanks, Aymeric. I grabbed the latest Django code and things worked like a charm.
Now, I have a decision to make: Stay on the Django/Python 3 bleeding edge or back off to Python 2.7. My project's timeline says I won't release until after Django 1.6 (even with some slop for slipping releases), but it still feels dicey. On the other hand, on a brand new project, I'd prefer to be looking at Python's future rather than sticking in its past. :) tj On Wednesday, May 8, 2013 5:26:41 AM UTC-6, Aymeric Augustin wrote: > > On 7 mai 2013, at 08:34, Aymeric Augustin > <[email protected]<javascript:>> > wrote: > > These problems look fairly easy. I plan to work on them. > > > I just updated the pull request and everything works except BinaryField: > https://code.djangoproject.com/ticket/20025#comment:5 > > Something forces the output to be a string, either in the MySQL connector > or in the converters registered by Django. > > I would appreciate some help on this. > > Here's how to setup the MySQL connector with python 3.3: > > $ pyvenv-3.3 mysql-py33 > $ . mysql-py33/bin/activate > $ curl http://python-distribute.org/distribute_setup.py | python > $ git clone https://github.com/clelland/MySQL-for-Python-3 > $ cd MySQL-for-Python-3 > $ python setup.py install > > Then run model_fields tests. > > -- > Aymeric. > > > > -- You received this message because you are subscribed to the Google Groups "Django developers" 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]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
