Update license specifier for PEP639#1808
Merged
zm711 merged 6 commits intoNeuralEnsemble:masterfrom Jan 29, 2026
Merged
Conversation
alejoe91
approved these changes
Dec 31, 2025
Contributor
Author
|
In addition the RTD is failing. It seems like it is not using an appropriate way of reading the license specifier.... I'll dig into this in a bit. |
Contributor
@zm711 I think it's PEP639, not 369. Right? https://peps.python.org/pep-0639/ |
alejoe91
reviewed
Jan 2, 2026
zm711
changed the title
Contributor
Author
|
Yes it is. I just typed wrong. Haha. |
Contributor
Author
|
I also updated python version numbering in the license and codemeta. We did that in #1807, but just didn't change the docs part of the license. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1793
As of PEP369, we should specify our license like this.
Testing might fail due to quantities (see #1807) for more info.