Re: Recommending a Python 3-compatible MySQL connector

2014/1/23 Daniel Sears > I know the core issue of GPL remains. But since this discussion began > Oracle has extended their driver to include their own > Django > back-end

Re: Recommending a Python 3-compatible MySQL connector

On Thu, Jan 23, 2014 at 2:51 PM, Daniel Sears 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 > : > > >- PEP 249-compliant >- pure Python

Re: Recommending a Python 3-compatible MySQL connector

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 : - PEP 249-compliant - pure Python - supports Python 3 - very simple installation: pip install

Re: Recommending a Python 3-compatible MySQL connector

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 wrote: > 2013/5/10 Aymeric Augustin >> >> > Also actively developed by @geertjanvdk at Oracle so he may

Re: Recommending a Python 3-compatible MySQL connector

2013/5/10 Aymeric Augustin > > 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 ma

Re: Recommending a Python 3-compatible MySQL connector

Hi Luke, Your blog post nails the problem. The GPL wasn't written with dynamic languages in mind and "linking" is a big question mark. As far as I know, it has never been tested in court, and we won't be sure of anything until it is. Of course I could be wrong… I'm just repeating what I've heard

Re: Recommending a Python 3-compatible MySQL connector

On May 10, 2013, at 11:49 AM, Luke Plant wrote: > On 10/05/13 14:12, Aymeric Augustin wrote: >> Hi Mark, >> >> On 10 mai 2013, at 10:16, Mark Hughes wrote: >>> Another option to consider could be mysql-connector-python >>> >>> https://pypi.python.org/pypi/mysql-connector-python/1.0.9 >> >> T

Re: Recommending a Python 3-compatible MySQL connector

On 10/05/13 14:12, Aymeric Augustin wrote: > Hi Mark, > > On 10 mai 2013, at 10:16, Mark Hughes wrote: >> Another option to consider could be mysql-connector-python >> >> https://pypi.python.org/pypi/mysql-connector-python/1.0.9 > > Thank you, it's the official library I was missing! > > Unfor

Re: Recommending a Python 3-compatible MySQL connector

Hi Mark, On 10 mai 2013, at 10:16, Mark Hughes wrote: > Another option to consider could be mysql-connector-python > > https://pypi.python.org/pypi/mysql-connector-python/1.0.9 Thank you, it's the official library I was missing! Unfortunately, it's licensed under the GPL. To the best of my und

Re: Recommending a Python 3-compatible MySQL connector

On 5 May 2013 19:17, Aymeric Augustin wrote: > > To claim first-class Python 3 support in Django 1.6, we need to recommend a > MySQL connector that works. This was discussed a few times on the mailing > list, now's the time to make a decision. Here's a summary of the options. > Another option t

Re: Recommending a Python 3-compatible MySQL connector

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),

Re: Recommending a Python 3-compatible MySQL connector

On 7 mai 2013, at 08:34, Aymeric Augustin 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

Re: Recommending a Python 3-compatible MySQL connector

On 6 mai 2013, at 23:38, Travis Jensen wrote: > On Sunday, May 5, 2013 2:46:43 PM UTC-6, Aymeric Augustin wrote: > On 5 mai 2013, at 21:15, Ian Clelland wrote: > > > I don't object at all -- as long as the code it still passing tests, that > > is :) > > > So, given that the tests aren't pa

Re: Recommending a Python 3-compatible MySQL connector

On Sunday, May 5, 2013 2:46:43 PM UTC-6, Aymeric Augustin wrote: > > On 5 mai 2013, at 21:15, Ian Clelland > > wrote: > > > I don't object at all -- as long as the code it still passing tests, > that is :) > > So, given that the tests aren't passing, what does that mean? I've played around w

Re: Recommending a Python 3-compatible MySQL connector

On 5 mai 2013, at 21:15, Ian Clelland wrote: > I don't object at all -- as long as the code it still passing tests, that is > :) I just installed your version of MySQL-for-Python-3 on the CI server. We'll have the results of the test runs in a few hours: http://ci.djangoproject.com/job/Django/

Re: Recommending a Python 3-compatible MySQL connector

> So, unless someone has a better idea, or Ian objects, I'm going to link to > his fork . I don't object at all -- as long as the code it still passing tests, that is :) It was originally developed as a proof of concept when python 3 support was bri

Recommending a Python 3-compatible MySQL connector

Hello, To claim first-class Python 3 support in Django 1.6, we need to recommend a MySQL connector that works. This was discussed a few times on the mailing list, now's the time to make a decision. Here's a summary of the options. Moist: https://github.com/farcepest/moist - port by Andy