Skip to content

  • No categories

Psf License Agreement

You can use the original (like everyone who receives from you) only under the conditions set by the license, at least by the usual courtesy that you must say to these conditions. Anyway, I don`t see what you would gain by omitting the license. Let him in and interpret him widely. Unless you`re trying to cheat one way or another, in this case you don`t have my sympathy, and you should ask a lawyer for the exact wobbly space available – Some software embedded in Python is under different licenses. Licenses are listed with the code that falls under this license. You will find an incomplete list of these licenses in licenses and confirmations for incorporated Software. Python Software Foundation License (PSFL) is a BSD-style free software license that is compatible with the GNU General Public License (GPL). [1] Its main use is the distribution of The Python project software. Unlike the GPL, the Python license is not a copyleft license and allows the distribution of modified versions without a source code. The PSFL is allowed on both the FSF`s list of licenses[1] and the list of approved OSI licenses.

Personally, I`m a fan of a central file that shares copyright information and several separate license files if necessary. Take a look at the combining code written under different licenses (Eiffel Forum license, MIT and Apache), what are my options? Starting with Python 3.8.6, examples, recipes and other codes are doubly conceded in the documentation under the PSF license agreement and the Zero-Clause BSD license. Guido van Rossum, the creator of Python, was awarded the 2001 Free Software Foundation award for the Advancement of Free Software[3] for changing the license to address this incompatibility. I want to fulfill the terms of the license of this code, which is the PSF LICENSE AGREEMENT FOR PYTHON 2.7.6, which says (in part) hashlib, posix, ssl, crypt use the OpenSSL library for additional performance when provided by the operating system. In addition, Windows and Mac OS X installers for Python may contain a copy of OpenSSL libraries, which is why we`re adding a copy of the OpenSSL license here: the standard library is also covered by the Python Software Foundation license. For more information, see the Lib/LICENSE file. Upon reading copyright by the Free Software Foundation, the creation of a derivative class creates a work derived from the original work, and therefore the license should be included. This definition is not universally accepted.

I understand that you feel that the license no longer exists in your repo. I wouldn`t worry too much about that. Just stick it together and make it clear what`s in it. The C14N 2.0 test collection in the test batch (Lib/test/xmltestdata/c14n-20/) was accessed on by the W3C website and distributed under the BSD 3 clause: if I comply with the other clauses (in particular Clause 3, I am completely compliant and I am not obliged to distribute a part of Python (especially the license or copyright) with my own code. In October 2000, Barry helped transfer the software to SourceForge, where it was renamed Jython. Jython 2.0 and 2.1 were developed under the specific jython license below. In 2000, Python was briefly available under the Python license, which is not compatible with THE GPL. The reason for this incompatibility by the Free Software Foundation was that “this Python license is subject to the laws of the State of Virginia in the United States,” which the GPL does not allow. [2] Compatible GPL does not mean that we distribute Python under the GPL.

Posted in Uncategorized.

0 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.