Fix pyproject.toml license classifier deprecation

[tmi]

Gets rid of the 'deprecated' warnings that pop up multiple times during build/install

Bumps setuptools requirement to accept the new license declaration format

Summary

Just a tiny PR, no change to API or code or anything. The license itself is as before, it just changes the manner in which it is declared -- as recommended by the PyPA guidelines https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license

I tried to find any issue related to this but found none. And I guess not worth it creating one

Test plan

Since this does not change any of the code, I just tested that the package can be installed/built as before via ./install_executorch.sh, and that the deprecation warnings vanish

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14592

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 14 New Failures

As of commit add7142 with merge base db8d04f ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t f1dcbc219e8d772d88d00164c5fddff1bd742f2b5351d02d785a529307e6cf3c /exec failed with exit code 1
• trunk / test-huggingface-transformers-macos (bert|coreml_fp32_gpu|--quantize) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 128
• trunk / test-huggingface-transformers-macos (distilbert|coreml_fp32_gpu|--quantize) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 128
• trunk / test-huggingface-transformers-macos (llama3.2-1b|coreml_fp32_gpu|--quantize) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 128
• trunk / test-huggingface-transformers-macos (olmo-1b|coreml_fp32_gpu|--quantize) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 128
• trunk / test-huggingface-transformers-macos (qwen3-0.6b|coreml_fp32_gpu|--quantize) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 128
• trunk / test-huggingface-transformers-macos (smollm2-135m|coreml_fp32_gpu|--quantize) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 128
• trunk / test-huggingface-transformers-xnnpack (gemma3-1b|xnnpack|--quantize) / linux-job (gh)
  RuntimeError: Command docker exec -t 015349dc60bd3f08f6927f92058dd2128ba9872a59cc0743c9aad46a13e4660c /exec failed with exit code 128
• trunk / test-huggingface-transformers-xnnpack (llama3.2-1b|xnnpack|--quantize) / linux-job (gh)
  RuntimeError: Command docker exec -t 58b80b4c1d8f4f50f2dbeb2ee1df90be99c5d747ee12e0cb833a228d8d0e92c2 /exec failed with exit code 128
• trunk / test-huggingface-transformers-xnnpack (phi4-mini|xnnpack|--quantize) / linux-job (gh)
  RuntimeError: Command docker exec -t 0a4fe150a3d035589ff2e9f6c5d919bdc947af86202912b9328c4d272bb48333 /exec failed with exit code 128
• trunk / test-huggingface-transformers-xnnpack (qwen3-0.6b|xnnpack|--quantize) / linux-job (gh)
  RuntimeError: Command docker exec -t 3de00c2d577519d89a89f0d908ded60b898bf90bd7ea9e2bee2847793d539dd8 /exec failed with exit code 128
• trunk / test-huggingface-transformers-xnnpack (qwen3-1.7b|xnnpack|--quantize) / linux-job (gh)
  RuntimeError: Command docker exec -t 6eccdec8fbf75d323dee799bd65ffac09717bde743fbc1c76e1c59b1d4995b29 /exec failed with exit code 128
• trunk / test-huggingface-transformers-xnnpack (smollm2-135m|xnnpack|--quantize) / linux-job (gh)
  RuntimeError: Command docker exec -t bac021a8fe5679469cf4d3e8ffdfe0a50fa08ce8b7aee25ff6e5506c296b1f7e /exec failed with exit code 128
• trunk / test-huggingface-transformers-xnnpack (smollm3-3b|xnnpack|--quantize) / linux-job (gh)
  RuntimeError: Command docker exec -t 6cd1499e243933c5da73ff51eefda6dd0f7134b74dc41493d57f0b853c63e6e3 /exec failed with exit code 128

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-cla]

Hi @tmi!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[tmi]

@pytorchbot label "topic: not user facing"

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[mergennachin]

Why did you upgrade setuptools?

[tmi]

@mergennachin without the lower bound, the license fields fail to be parsed -- the first CI run failed because of that (as the runner defaulted to a cached version, 60-smth). I just grabbed the bound from a similar issue vllm-project/vllm#17389. I can leave a comment in the pyproject.toml linking the PEP that requries this bound. Thinking of it, we may also want to add an upper bound

The failures of the recent runs, like cannot import name 'PerBlock' from 'torchao.quantization.pt2e' or ValueError: QNN backend is not available. are not related, right? Or is it possible that the setuptools bump caused some silent failure of a prerequisite build?

[mergennachin]

Okay got it

That seems to be the right version.

The other failures seem unrelated.

Please also update https://github.com/pytorch/executorch/blob/main/requirements-dev.txt

[mergennachin]

Test failures for "Test CUDA Builds" look legit

Can you also update packaging>=24.2 in here?

executorch/pyproject.toml

Line 61 in 7ed9266

"packaging",

[tmi]

Test failures for "Test CUDA Builds" look legit. Can you also update packaging>=24.2 in here?

right, thx. I updated it, but in the build-system's requirements, not in the depedendencies -- I think thats more suitable place, given the test failure. Not sure if the runtime packaging dependency needs a lower bound too since there is no runtime setuptools dependency -- I'd guess not

[mergennachin]

Thank you @tmi

[mergennachin]

@pytorchbot cherry-pick --onto release/1.0 -c release --fixes "upgrades setuptools and packaging to improve logs during installation/build"

[pytorchbot]

Cherry picking #14592

The cherry pick PR is at #14761 and it is linked with issue upgrades setuptools and packaging to improve logs during installation/build. The following tracker issues are updated:

• [v1.0.0] Release Tracker #14288 (comment)

Details for Dev Infra team

Raised by workflow job