I want to follow up on the issue of a Python 3 connector for MySQL. Oracle has developed an open source Python driver for MySQL<http://dev.mysql.com/doc/connector-python/en/index.html> :
- PEP 249-compliant - pure Python - supports Python 3 - very simple installation: pip install mysql-connector - better support for asyncio than a C driver<https://www.devbliss.com/en/reviving-the-snake/> - stable - actively developed and supported by Oracle - will likely track emerging MySQL features (in line with Oracle's other drivers, e.g. Java, PHP, ...) I submitted a documentation patch<https://docs.djangoproject.com/en/dev/ref/databases/#mysql-db-api-drivers> for this a few months ago, but then I saw this closed ticket<https://code.djangoproject.com/ticket/21226>. So I want to revisit this issue in the hopes of getting a clarifying policy. Without that I should probably back out the patch. I know the core issue of GPL remains. But since this discussion began Oracle has extended their driver to include their own <http://dev.mysql.com/doc/refman/5.6/en/connector-python-django-backend.html>Django back-end<http://dev.mysql.com/doc/refman/5.6/en/connector-python-django-backend.html>. Does this create enough separation to get us out of the GPL bind? --Dan On Wednesday, June 5, 2013 9:11:11 AM UTC-7, Jacob Kaplan-Moss wrote: > > I've reached out to a lawyer friend to see if he can give us some > guidance. Until then, let's avoid making a recommendation either way. > > Jacob > > On Wed, Jun 5, 2013 at 10:01 AM, Aymeric Augustin > <[email protected] <javascript:>> wrote: > > 2013/5/10 Aymeric Augustin <[email protected] <javascript:>> > > >> > >> > Also actively developed by @geertjanvdk at Oracle so he may be able > to > >> > help with any issues? > >> > >> If he has the power to switch to a license that makes it possible to > use > >> his code, like the LGPL, that would be fantastic. I can't tell if he > chose > >> the GPL to make a point or by accident; I'm going to ask him. > > > > > > I got an answer today. The license will not be changed. I was asked not > to > > publish our discussion. > > > > Specifically, MySQL Connector/Python is released under GNU GPLv2 with > FOSS > > exception. > > > > The FOSS exception only applies to redistributing MySQL > Connector/Python, > > which we don't intend to do anyway. > > > > > > To sum up, the scenario I'm worried about is the following. A company > > develops a product based on Django + MySQL and distributes it to its > > customers. Currently, the product can be distributed under any license. > If > > we switch to MySQL Connector/Python in Django, then the product must be > > licensed under the GPLv2 or a compatible license. Once again I'm not a > > lawyer and I may be wrong, I don't know where the line lies exactly, but > > that could create a legal trap for some users of Django. > > > > I don't want to add a warning along the lines of "be careful, if you use > > MySQL, the licensing terms change!" in our docs. I'm not even sure how > to > > write it without falling into FUD. > > > > So at this point I see two solutions: > > - a core dev (not me!) feels sufficiently confident that this isn't an > issue > > to add such a backend to Django itself. That's Oracle's theory, as far > as I > > understand. > > - someone writes an external MySQL Connector/Python backend, probably > based > > on the MyQSLdb backend. That keeps the licensing issue outside of > Django. > > > > I'm leaving this here, if someone wants to take over, the ground is > yours! > > > > -- > > 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] <javascript:>. > > To post to this group, send email to > > [email protected]<javascript:>. > > > Visit this group at > http://groups.google.com/group/django-developers?hl=en. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- 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/d84939dd-3428-44d0-ac0a-74aaff8140ff%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
