chore: align package metadata with Apache-2.0 license - #477
Open
ilmioalias wants to merge 1 commit into
Open
ilmioalias wants to merge 1 commit into
ilmioalias wants to merge 1 commit into
Conversation
Update README, Sphinx docs badge, and setup.cfg classifiers/license field to reflect the Apache-2.0 license already in LICENSE. No algorithm, dependency, or version changes.
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
1 participant
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.
Summary
The repository
LICENSEwas changed to Apache-2.0, but the README, Sphinxdocumentation, and Python package metadata still referenced GPL-3.0. This
PR aligns those surfaces with the current license so it is unambiguous
that PyPop7 is distributed under Apache-2.0.
Scope is limited to licensing/documentation/metadata. No algorithm,
dependency, or version changes.
Changes
README.md: replaced the GPL-3.0 licensing statement with anApache-2.0 statement pointing to the
LICENSEfile.docs/sphinx/source/index.rst: replaced the GPL-3.0 shields.io badgewith an Apache-2.0 badge (same
LICENSEtarget link).setup.cfg: removed theLicense :: OSI Approved :: GNU General Public License v3 or later (GPLv3+)classifier, added
License :: OSI Approved :: Apache Software License,and added
license = Apache-2.0.pyproject.toml: no change needed — the project has no[project]table (metadata lives entirely in
setup.cfg), so there is noconflicting license declaration to reconcile.
Validation
python -m build— succeeds (sdist + wheel).python -m twine check dist/*— PASSED.METADATA: no GPL classifier present,License :: OSI Approved :: Apache Software Licensepresent.grep -RniE 'GPL-3\.0|GPLv3|GNU General Public License'across therepository: the only remaining match is an unrelated third-party
attribution comment in
pypop7/optimizers/es/_repeat_saes.pyreferringto external MATLAB code, not the project's own license — left
untouched intentionally.
Notes
This PR does not publish a PyPI release. The currently published PyPI
package (
0.0.82) still declares GPL-3.0, since it predates thismetadata alignment; a maintainer will need to cut a new release once
this is merged for the corrected metadata to reach PyPI.