Generated by GPT-5-mini| PSF License | |
|---|---|
![]() | |
| Name | PSF License |
| Author | Python Software Foundation |
| Date | 2000s |
| Status | Active |
PSF License The PSF License is a permissive software license associated with the Python Software Foundation and closely connected to distribution of the Python programming language and related libraries. It has been referenced in discussions involving the Open Source Initiative, Free Software Foundation, Debian Project, and other organizations that govern software distribution, relicensing, and compatibility among major projects.
The PSF License emerged as part of licensing efforts by the Python Software Foundation during transitions involving the Python Software Foundation, Guido van Rossum, and corporate contributors such as Corporation for National Research Initiatives and CNRI. It appears alongside landmark events and documents in software licensing history like the creation of the Open Source Initiative, the GNU General Public License debates involving Richard Stallman, and the Debian Social Contract deliberations. Over time the license intersected with notable institutions and projects including the Free Software Foundation, Debian Project, GNU Project, Fedora Project, Ubuntu Foundation, Apache Software Foundation, Mozilla Foundation, Eclipse Foundation, and various universities and research labs.
The PSF License contains clauses addressing copyright attribution, redistribution, warranty disclaimer, and permissive reuse. These provisions have been compared to terms found in the MIT License, BSD License, and ISC License as interpreted by organizations such as the Open Source Initiative, Free Software Foundation, and Software Freedom Law Center. Legal practitioners at entities like the Software Freedom Conservancy, Electronic Frontier Foundation, and academic legal clinics at Harvard Law School and Stanford Law School have analyzed its language relative to contract law decisions in courts such as the United States Court of Appeals and the Supreme Court of the United States, and in jurisdictions including the United Kingdom, Germany, France, Australia, and Japan.
Multiple textual variants of the license exist, reflecting edits for attribution requirements, export control statements, and compatibility notes. These variants have been reviewed by communities centered on projects like CPython, PyPI, setuptools, pip, Django Software Foundation, NumPy Project, SciPy Community, and Jupyter Project. License text revisions have been scrutinized by package maintainers in distributions such as Debian, Fedora, Arch Linux, Gentoo, OpenSUSE, and by commercial vendors including Red Hat, Canonical, Microsoft, Google, Amazon, and Oracle.
Compatibility considerations have involved comparisons with the GNU General Public License, LGPL, Mozilla Public License, Apache License, and permissive licenses used by projects including Node.js Foundation, Ruby Core Team, Perl Foundation, and R Foundation for Statistical Computing. Legal advisories have referenced international treaty frameworks and statutory regimes when assessing redistribution, relicensing, and patent grants for contributors associated with institutions like CERN, NASA, National Institutes of Health, and the European Commission. Organizations such as the Open Source Initiative, Free Software Foundation, SPDX Workgroup, and GitHub Legal have catalogued compatibility matrices impacting integration with proprietary platforms from companies like IBM, Facebook, Intel, Qualcomm, and NVIDIA.
The license is used in many Python-related packages and has been adopted by dozens of projects in scientific computing, education, and web development, including repositories maintained by contributors from universities such as Massachusetts Institute of Technology, University of California Berkeley, Carnegie Mellon University, and institutions like Lawrence Berkeley National Laboratory. Ecosystem adopters include package authors on PyPI, platform maintainers at Anaconda, Continuum Analytics, Enthought, and organizations using Python in production such as NASA Jet Propulsion Laboratory, CERN experiments, financial firms like Goldman Sachs and Morgan Stanley, and tech companies including Dropbox, Instagram, YouTube, and Spotify.
Critiques have come from free software advocates and legal scholars who compare the license’s wording to prominent controversies involving license proliferation, dual licensing, and relicensing disputes exemplified by cases involving the GNU Project, Oracle v. Google, and license interpretation debates in communities like Debian and Fedora. Discussions in public fora linked to influential figures and institutions such as Linus Torvalds, Richard Stallman, the Open Source Initiative, the Free Software Foundation, and academic commentators have highlighted concerns about clarity, compatibility, and enforceability in cross-jurisdictional contexts.