[Python-Dev] (Licensing question) PSF license (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Fri Mar 15 07:06:08 EDT 2019
- Previous message (by thread): [Python-Dev] (Licensing question) backport of shutil.copyfile() functionality
- Next message (by thread): [Python-Dev] Reminder: Python Language Summit 2019 Signup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 12 Mar 2019 01:27:14 -0400 Terry Reedy <tjreedy at udel.edu> wrote:
> First of all, I'm sorry if I'm wrong. I'm not lawyer. > > You can use both of GPL and MIT. Users can use your package under it. > > On the other hand, when you publish your package, you should follow > PSF license. > Read this. https://docs.python.org/3/license.html > > """ > 3. In the event Licensee prepares a derivative work that is based on or > incorporates Python 3.7.2 or any part thereof, and wants to make the > derivative work available to others as provided herein, then Licensee hereby > agrees to include in any such work a brief summary of the changes > made to Python > 3.7.2. > """ > > As you can see, PSF license doesn't force you to use PSF license. (not > "copyleft")
In fact, the PSF lawyer says one should not use the 'PSF license' as it is specilized for the PSF and Python.
Interesting. I did use the PSF license for the pickle5 backport and I suspect I'm not the only one to use it (though I don't know how to do a per-license search on PyPI). https://pypi.org/project/pickle5/
Regards
Antoine.
- Previous message (by thread): [Python-Dev] (Licensing question) backport of shutil.copyfile() functionality
- Next message (by thread): [Python-Dev] Reminder: Python Language Summit 2019 Signup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]