Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License Offerings #58

Closed
alexggordon opened this issue Oct 14, 2015 · 6 comments
Closed

License Offerings #58

alexggordon opened this issue Oct 14, 2015 · 6 comments

Comments

@alexggordon
Copy link

Hello! Recently, I started working through building my own Python 3 support for MySQLdb. However, before I started doing so I had come across a post by the original author, @farcepest on Sourceforge about how users could optionally use the CNRI license (I've copied the post here in case it disappears for some reason).

I think given your work on MySQLdb, and given that @farcepest originally offered it, I think it would be really cool if you would extend that offer onto the users of mysqlclient-python.

In @farcepest's post, he mentions that this CNRI offering applies to versions of MySQLdb lower than 1.3, (mysqlclient-python forked MySQLdb at version 1.2).

The gist of the offering would be allowing the users to choose either the CNRI license, or GPL2. That said though that could get a little confusing, but is a really nice choice I think.

Do you have any thoughts on the issue?

@methane
Copy link
Member

methane commented Oct 14, 2015

About using MySQLdb as import MySQLdb, your app can select any license you want.

About distributing MySQLdb, I don't think dual licensing doesn't have meaning since MySQLdb
requires libmysqlclient and libmysqlclient is distributed on GPLv2.

Is this enough for you?

@JukkaHonkola
Copy link

Is this correct? I see that the LICENCE file defines the licence as GPLv2, not LGPL. Thus, in my understanding any program that imports MySQLdb would also be GPLv2. This would cause any program using MySQLdb to be licenced under GPLv2.

@methane
Copy link
Member

methane commented Dec 5, 2015

Yes. MySQLdb uses MySQL Connector/C. It's GPLv2.

This is not a problem when you use MySQL-python on server.
You don't required to make your server-side application open to end users. (Sinse GPL is not AGPL.)

@methane methane closed this as completed Dec 5, 2015
@photonbit
Copy link

I see this issue is marked as closed, but maybe it shouldn't. There is a MySQL Connector/C version that is LGPL and the new MariaDB Connector/C is LGP by default, so this option should be considered for the python library too.

@methane
Copy link
Member

methane commented Dec 14, 2015

To change license, acknowledgement of original owner (@farcepest) is required.
Since he is inactive for very long, I think it's very hard.

Since I'm not a lawyer, I may be wrong. But I don't like to pay time and power for licensing issue.

@antoncohen
Copy link

Sorry to dig up an old issue. The original MySQLdb is dual licensed, GPLv2 and Old Python license (CNRI Python License).

MySQL is GPLv2, but it has a licensing exception for FOSS software, with CNRI Python License listed as one of the allowed licenses. This is really important, because it allows MySQL client wrapper libraries (like mysqlclient-python) to be licensed under a liberal license, and then projects like Django can use the wrapper libraries.

It looks like mysqlclient-python is still licensed under the CNRI Python License, as seen at the bottom of INSTALL.rst.

It would be nice if this information what in a more prominent place, it would be extra nice if PyPI listed it as one of the licenses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants