Twine uploads with `provides_extras` field, not `provides_extra`

[Dustin Ingram]

Is there an existing issue for this?

• I have searched the existing issues (open and closed), and could not find an existing issue

What keywords did you use to search existing issues?

provides_extra, provides_extras

What operating system are you using?

Other

If you selected 'Other', describe your Operating System here

No response

What version of Python are you running?

$ python --version
Python 3.11.8

How did you install twine? Did you use your operating system's package manager or pip or something else?

$ python -m pip install twine

What version of twine do you have installed (include the complete output)

$ twine --version
twine version 5.0.0 (importlib-metadata: 7.0.1, keyring: 24.3.0, pkginfo: 1.10.0, requests: 2.31.0, requests-toolbelt: 1.0.0, urllib3: 2.1.0)

Which package repository are you using?

PyPI

Please describe the issue that you are experiencing

Twine does not correctly POST the Provides-Extra field when it is present in package metadata.

Please list the steps required to reproduce this behaviour

1. Build a package with Provides-Extra metadata field (example);
2. Upload it with twine;
3. Observe that twine POSTs the field provides_extras, and not provides_extra;
4. Observe that PyPI does not record the Provides-Extra values.

Anything else you'd like to mention?

I introduced this bug six years ago, so my apologies 🙂.

[Ian Stapleton Cordasco]

Easy one to make. Should be easy to fix

[Javan Lacerda]

On it