I'd like see some community consensus on the best solution for a MySQL adapter rather than than have more than one build for MySQL.
I don't know the MySQL ecosystem very well. Naoki, is there no interest from MySQLdb in your Python 3 compatibility changes? On the PyPI page it says, "Python-3.0 will be supported in a future release." but it's been like that for several years so who knows if it's actually going to happen. I think we could at least consider a change from the (somewhat random?) Python 3 fork of MySQLdb we are using for the Python 3 bulids. On Friday, June 6, 2014 12:44:12 PM UTC-4, Collin Anderson wrote: > > While we're on the topic, I'd like to propose (also?) supporting the > pure-python, MySQLdb-compatible pymysql, which INADA Naoki (methane) has > also put a lot of work into. > > pymysql is pure-python, so it's really easy to get up-and running on Mac > OS X and in other environments, because you don't need the mysql header > files around. Just pip install pymysql, and you're good to go. > > https://code.djangoproject.com/ticket/22391 > > Tim says on the ticket: "One question I have is how we are going to ensure > that it doesn't break if we merge it to core. Do we need another MySQL > build to the Jenkins matrix?" > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/52e8bf42-28fa-4f3b-a654-74965d517852%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
