pypa / pypa/setuptools

[FR] Remove License classifier warning

Open
#4,938 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Needs Triage
Dominant language
Python
Stars
2.9k
Forks
1.4k
Avg merge
1d 1h
Merged PRs (30d)
1

Description

What's the problem this feature will solve?

setuptools v77.0.0 now prints a large deprecation warning when using License:: classifiers, even if the new license key in pyproject.toml is not used. This presents a problem for ansible. We can't adopt the new standard, as we don't store configuration in pyproject.toml (we use setup.cfg) and do not maintain a cumulative SPDX license expression that encompasses the additional GPL-compatible licenses present in the 80+ Ansible collections included in the ansible package, so we could not add an accurate license key (GPL-3.0-or-later by itself would be incomplete) even if we wanted to move our configuration. Printing this loud warning is unhelpful to us.

Describe the solution you'd like

Please consider removing this deprecation warning or maybe only raising it when configuration is sourced from pyproject.toml. It's not actionable and creates backwards compatibility issues.

Alternative Solutions

Removing the classifiers and not moving our config to pyproject.toml, but this would result in an overall loss in license metadata

Additional context

Thank you for working on setuptools!

Code of Conduct
  • I agree to follow the PSF Code of Conduct

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named in the issue. Start by locating where setuptools emits the License classifier deprecation warning and how configuration sources are distinguished, then inspect existing tests around that warning; done means an agreed behavior that avoids the reported warning without losing license metadata.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.