On Thu, Jan 23, 2014 at 2:51 PM, Daniel Sears <daniel.se...@gmail.com>wrote:
> 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? > The existence of a Django backend in MySQL Connector/Python doesn't change anything. The code is still released under the GPL, and the GPL has been specifically constructed to prevent people from "getting out of it". The issue is that the GPL is at odds with the type of community that the Django project has tried to foster. Django has been released under the terms of the BSD license specifically because we want to allow commercial activities without also requiring the release of source code. If we recommended MySQL Connector/Python backend, anyone who chose to use that backend would need to release that project under the terms of the GPL - which means releasing source code. This may be acceptable on a per project basis, and users are free to use Connector/Python in their own projects if they want -- but I don't think Django as a project should be encouraging this by documenting it as an option. Yours, Russ Magee %-) -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/CAJxq848Wo4p1aDrPigBtgzH%2BFTkdMua2VH9%2BqChdCpFtDjin_g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
