Skip to content

Conversation

mbfreder
Copy link
Contributor

@mbfreder mbfreder commented Aug 8, 2025

Which issue(s) does this change fix?

License classifiers are deprecated. When running python setup.py --version command is run internally, it also returns a deprecation warning message instead of just the version number, causing a parsing issue. The change on this PR fixes the issue.

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

Why is this change necessary?

How does it address the issue?

What side effects does this change have?

Mandatory Checklist

PRs will only be reviewed after checklist is complete

  • Add input/output type hints to new functions/methods
  • Write design document if needed (Do I need to write a design document?)
  • Write/update unit tests
  • Write/update integration tests
  • Write/update functional tests if needed
  • make pr passes
  • make update-reproducible-reqs if dependencies were changed
  • Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@mbfreder mbfreder requested a review from a team as a code owner August 8, 2025 18:29
@@ -65,7 +65,6 @@ def read_version():
"Environment :: Other Environment",
"Intended Audience :: Developers",
"Intended Audience :: Information Technology",
"License :: OSI Approved :: Apache Software License",
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we replace this with something else? Is there a new alternative to do this instead of the old License classifier?

If this is currently visible on the generated package, we don't want to just suddenly stop adding the license information.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The license is already included here.

@mbfreder mbfreder added this pull request to the merge queue Aug 8, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 8, 2025
@mbfreder mbfreder added this pull request to the merge queue Aug 11, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 11, 2025
@seshubaws seshubaws enabled auto-merge August 27, 2025 18:12
@seshubaws seshubaws added this pull request to the merge queue Aug 27, 2025
Merged via the queue into aws:develop with commit d006933 Aug 27, 2025
50 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants