Python-2.0 is the historic CNRI/BeOpen stack SPDX uses for older Python. PSF-2.0 is the current CPython grant. They are not the same text.
On this page
What it does
SPDX's Python-2.0 identifier covers the composite of CNRI, BeOpen and earlier Python grants that shipped with Python 2.0. Current CPython uses PSF-2.0. GPL compatibility differs between the historic stack and PSF-2.0. If a wheel still declares Python-2.0, keep that id and that text. Do not silently map it to MIT or to PSF-2.0 in the SBOM.
Pros
- Easy to drop into a closed, paid product. Procurement has seen this family many times.
- No copyleft on your own files. You keep your source private.
Cons
- The notice duty is easy to miss in a desktop, mobile, or container build. A web page is not a substitute for notices inside the artifact.
- Transitive copies in the lockfile count. Listing only direct dependencies leaves notices out.
What it allows and requires
Choose a category to see the full grant in one scannable list. Permissions show what the license allows, limits show what it withholds, and obligations show the conditions your release process must satisfy.
Permissions
Commercial use
You may ship the code inside a paid product. The license does not restrict commercial use.
Modify
You may change the code, including keeping those changes private, unless a later obligation says otherwise.
Distribute
You may give copies to others. Distribution is what usually turns notice and source duties into real work.
Sublicense
You may include the code under your own product terms, so long as you still meet this license's conditions.
Private use
Use inside your company, including internal forks, does not by itself trigger distribution duties.
Limits
Hold liable
The authors disclaim warranty. Recipients cannot hold them liable for damages arising from the software, except where law forbids that disclaimer.
Use trademark
The license is not a trademark license. Names, logos and product marks stay with their owners unless a separate grant says otherwise.
Patent grant
The text does not grant patents. If buyers want an express patent grant, Apache-2.0 is the usual alternative.
Obligations
Include copyright
Keep the copyright line with every copy or substantial portion you distribute.
Include license
Keep the license text with every copy or substantial portion you distribute. A web page is not a substitute for notices inside a shipped artifact.
What Python-2.0 requires when you ship
When a copy that includes Python-2.0 code leaves your company, the grant is broad and the paperwork is easy to miss. Distribution here means an installer, a mobile binary, a container image, or an SDK another team embeds. Work this list against the artifact you actually hand over, not against a README. A hosted service that never gives out a copy still belongs on the record, but the notice duty does not fire until a copy exists.
You meet the notice condition when each Python-2.0 component's copyright line and license text appear in the material the recipient actually gets.
You are done for a hosted service that never hands out a copy. Running the software for users over a network does not, by itself, trigger a notice duty.
You are covered for a desktop, mobile or on-premise build when the notices sit inside the artifact. An about screen or a bundled licenses file both work.
The duties named in Python-2.0
The license text itself is short. These are the named conditions. They follow the code, including files you vendor into your own repository and transitive packages in the lockfile.
Include copyright
Keep the copyright line with every copy or substantial portion you distribute.
Include license
Keep the license text with every copy or substantial portion you distribute. A web page is not a substitute for notices inside a shipped artifact.
Things to be aware of
- Reading Python-2.0 as no obligations at all and shipping a binary with no notices in it. Put the notices in the artifact you hand over.
- Deleting the license header when you copy one or two files into your own repository. The condition follows the code, not the package it came in.
What the Python License 2.0 does not do
Search results often flatten Python License 2.0 into a slogan. These are the usual misreads. Python-2.0 is a grant with conditions, not a permission to skip the paperwork below.
- Python-2.0 does not mean no obligations. The copyright line and the license text still have to travel with copies you distribute.
- Python-2.0 does not force you to open your own source. There is no copyleft here unless a later clause in this text says otherwise.
How Python-2.0 differs from nearby licenses
These licenses are often confused with Python-2.0, but their release duties differ. Each row summarizes what the license requires when you ship. Open the linked page for the full checklist.
- Python-2.0
- Python-2.0 is the historic CNRI/BeOpen stack SPDX uses for older Python. PSF-2.0 is the current CPython grant. They are not the same text.
- PSF-2.0
- The license behind CPython and the standard library. Permissive, but a derivative work you distribute has to include a brief summary of your changes.
- MIT
- MIT lets you ship the code inside a closed, paid product. The one condition is that the copyright line and license text travel with every copy.
- GPL-2.0-or-later
- GPL-2.0 asks for source when you hand someone a binary. Running it on your own servers triggers nothing. The trigger is shipping a copy, not merely using it.
Common questions about Python License 2.0
Answers to common questions about what Python License 2.0 requires, when its duties apply, and what evidence belongs with a release.
What is the Python License 2.0?
SPDX's Python-2.0 identifier covers the composite of CNRI, BeOpen and earlier Python grants that shipped with Python 2.0. Current CPython uses PSF-2.0. GPL compatibility differs between the historic stack and PSF-2.0. If a wheel still declares Python-2.0, keep that id and that text. Do not silently map it to MIT or to PSF-2.0 in the SBOM.
What does Python-2.0 require when you ship a product?
You meet the notice condition when each Python-2.0 component's copyright line and license text appear in the material the recipient actually gets. You are done for a hosted service that never hands out a copy. Running the software for users over a network does not, by itself, trigger a notice duty. You are covered for a desktop, mobile or on-premise build when the notices sit inside the artifact. An about screen or a bundled licenses file both work.
Does Python-2.0 require me to open my own source?
Python-2.0 does not force you to open your own source. There is no copyleft here unless a later clause in this text says otherwise.
How do I attribute Python-2.0 in a product I ship?
Attribution for Python-2.0 means the copyright line and the license text travel with every copy a recipient actually gets. That can be an about screen, a licenses file inside the installer, or a notice in the container image. A public page helps a buyer audit the inventory. It does not replace notices inside the artifact. If you copied files into your own repository, the header on those files still has to stay.
Is a website notice enough for Python-2.0?
No. Python-2.0 talks about copies. A public attestation page is the honest list for procurement. The condition is met when the notices sit in the material you hand over. Put them in the installer, the about screen, or a licenses file inside the binary, then keep the same texts on the page.
Do transitive Python-2.0 dependencies count?
Yes. The condition follows the code, not the package you chose by name. If the lockfile pulled in Python-2.0 transitively and you distribute that tree, those notices travel too. Listing only direct dependencies is how teams miss the duty.
How is Python-2.0 different from Python Software Foundation License 2.0?
Python-2.0 asks this: Python-2.0 is the historic CNRI/BeOpen stack SPDX uses for older Python. PSF-2.0 is the current CPython grant. They are not the same text. Python Software Foundation License 2.0 asks this: The license behind CPython and the standard library. Permissive, but a derivative work you distribute has to include a brief summary of your changes. Open the Python Software Foundation License 2.0 page for what that license requires when you ship. Do not treat the SPDX ids as interchangeable because the short names look similar.
Where do I record Python-2.0 for a buyer?
Python-2.0 is a notice license in the catalog, so a component under it needs license text attached before it counts as live on your published page. SourceTrust fetches the published artifact, extracts the license file, and compares that text against the declared SPDX id. A match fills the text in. Every other outcome waits for a person. The stored text is what your page and each export file carry.
Where do I record Python-2.0 for a buyer?
Python-2.0 is a notice license in the catalog, so a component under it needs license text attached before it counts as live on your published page. SourceTrust fetches the published artifact, extracts the license file, and compares that text against the declared SPDX id.
A match fills the text in. Every other outcome waits for a person.
The stored text is what your page and each export file carry. Read /docs/auto-fetch-license for how the fetch works.
See also
The hub is the pillar for this cluster. Sibling licenses are the other spokes. Product FAQ links explain how SourceTrust records the duty, not the license text itself.
Practical guidance for procurement review, not legal advice. Confirm high-stakes use with counsel.