Skip to content

Cleanup metadata#201

Merged
jared321 merged 3 commits into
mainfrom
153Metadata
Jun 24, 2026
Merged

Cleanup metadata#201
jared321 merged 3 commits into
mainfrom
153Metadata

Conversation

@jared321

@jared321 jared321 commented May 22, 2026

Copy link
Copy Markdown
Contributor

PR Self-review

  • Review all changes
  • Build sdist and wheel
    • Confirm that license specification warning is not printed during build
    • Confirm that for each distribution the license is still provided and metadata is correct
  • Spot check action logs and confirm no sign of license specification warning
  • Confirm all actions passing

This most important change was the removal of the classifier that specified the
license, which was causing tools to emit a license deprecation warning.
@jared321 jared321 self-assigned this May 22, 2026
@jared321

jared321 commented May 22, 2026

Copy link
Copy Markdown
Contributor Author

@mosesyhc Can you please review the changes made so far in this PR and finalize in this PR the full set of metadata classifiers in setup.py? The current set of valid classifiers at here.

@mosesyhc mosesyhc left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good to me. Two minor questions:

  1. Do we not need the MIT license classifier because of the license field?
  2. Do we need the Framework :: tox classifier? Is it useful at all?

@jared321

jared321 commented May 22, 2026

Copy link
Copy Markdown
Contributor Author

Do we not need the MIT license classifier because of the license field?

The removal of this specific classifier was suggested in many action logs as part of building distributions

********************************************************************************
Please consider removing the following classifiers in favor of a SPDX license expression:

License :: OSI Approved :: MIT License

See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
********************************************************************************

Naively I suspect that the main goal is for packages to specify the license in only one place.

Do we need the Framework :: tox classifier? Is it useful at all?

Good question. I would guess not since this package does not provide any functionality to the tox world nor does it provide any functionality to package users directly via tox. Rather tox is something that developers access behind the scenes through clones of the surmise repo.

Do you want people to find surmise by filtering out only those packages in PyPI that mention tox in their metadata?

@mosesyhc

Copy link
Copy Markdown
Member

Thanks for the background info on the license.

I agree the addition of tox does not add much value. We can leave it out.

@jared321 jared321 merged commit a9fa1a7 into main Jun 24, 2026
56 checks passed
@jared321 jared321 mentioned this pull request Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants