docs: Add Environment :: WebAssembly :: Emscripten PyPI trove classifier

[matthewfeickert]

Description

Add PyPI trove classifiers to the PyPI metadata for Environment :: WebAssembly :: Emscripten as pyhf can run on a WASM build of CPython.

• c.f. https://discuss.python.org/t/do-we-want-classifiers-for-webassembly-on-pypi/22712

Thanks to @treyhunner for sharing this on Twitter and to @brettcannon for adding them in pypa/trove-classifiers#129. 👍

Checklist Before Requesting Reviewer

• Tests are passing
• "WIP" removed from the title of the pull request
• Selected an Assignee for the PR to be responsible for the log summary

Before Merging

For the PR Assignees:

• Summarize commit messages into a comprehensive review of the PR

* Add the PyPI Environment :: WebAssembly :: Emscripten trove classifier
  to the PyPI metadata as pyhf can run on a WASM build of CPython.
   - c.f. https://discuss.python.org/t/do-we-want-classifiers-for-webassembly-on-pypi/22712
* Update hatchling lower bound to v1.13.0, the first version to support
  the Environment :: WebAssembly trove classifiers.

[matthewfeickert]

@henryiii maybe we should add these to all the Scikit-HEP packages that currently work in pyodide?

[matthewfeickert]

I opened up pypa/hatch#725 as Environment :: WebAssembly isn't a valid classifier in the latest hatchling.

[matthewfeickert]

This will also require bumping

[build-system]
- requires = ["hatchling>=1.0.0", "hatch-vcs"]
+ requires = ["hatchling>=1.12.3", "hatch-vcs>=0.3.0"]  # c.f. PR #2100

assuming this fix would get into v1.12.3 (also throwing in a lower bound on hatch-vcs as might as well).

[brettcannon]

To be clear, Environment :: WebAssembly should only be specified if a package will work in both WASI and Emscripten (i.e. Pyodide). If your project only works with Emscripten/Pyodide, then use the Environment :: WebAssembly :: Emscripten classifier.

[matthewfeickert]

Suggested change

	"Environment :: WebAssembly",
	"Environment :: WebAssembly :: Emscripten",
	"Environment :: WebAssembly :: WASI",
	"Environment :: WebAssembly :: Emscripten",

As @brettcannon reminds me, NumPy and SciPy work with Emscripten, but they don't cleanly work with WASI in a way that would merit the WASI support classifier.

[codecov]

Codecov Report

Base: 98.30% // Head: 98.30% // No change to project coverage 👍

Coverage data is based on head (eb0aae6) compared to base (29fb68e).
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2100   +/-   ##
=======================================
  Coverage   98.30%   98.30%           
=======================================
  Files          69       69           
  Lines        4531     4531           
  Branches      645      645           
=======================================
  Hits         4454     4454           
  Misses         45       45           
  Partials       32       32           

Flag	Coverage Δ
contrib	97.88% <ø> (ø)
doctest	61.15% <ø> (ø)
unittests-3.10	96.31% <ø> (ø)
unittests-3.8	96.33% <ø> (ø)
unittests-3.9	96.35% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[matthewfeickert]

I'm going to approve and merge this myself. As always, PRs approved by a single core dev can be reverted as needed by the rest of the dev team.