Python License

Key characteristics

• The license granted permission to use, modify and redistribute Python source code, including for commercial purposes.
• It was generally regarded as compatible with the GNU General Public License in practical terms and so allowed combinations with GPL-covered code in many situations.
• Some of its wording — for example, jurisdiction or attribution clauses — made it less convenient than simpler permissive licenses, prompting later changes.

History and development

The Python License originated in the era before the Python Software Foundation established a standard, broadly accepted license. It was associated with the organization that stewarded Python at the time and covered multiple early releases. Over time the Python community evaluated license clarity, compatibility, and international applicability and moved toward a cleaner, more widely understood permissive approach.

Legacy and replacement

Because of concerns about phrasing and jurisdictional clarity, the original Python License was replaced for modern releases by the Python Software Foundation (PSF) license and other permissive licenses that are simpler to apply worldwide. The new terms removed ambiguities and made Python's licensing easier to reconcile with other open-source projects.

Notable distinctions

The historical Python License is distinct from copyleft licenses like the GPL and from modern permissive licenses such as BSD-style terms. It occupies a transitional place in open-source licensing history: functional for early distribution, but ultimately superseded for reasons of legal clarity and community compatibility. For general information about open-source license categories see open-source license resources.