-
-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add Environment :: WebAssembly and Framework :: Pydantic to trove classifiers #725
feat: Add Environment :: WebAssembly and Framework :: Pydantic to trove classifiers #725
Conversation
@ofek this is ready for review whenever you have time. |
Can you please instead run this Line 131 in 8a9ba20
|
8e65ba3
to
766a256
Compare
Yup. This now reflects the state of $ hatch env run --env backend update-classifiers |
Similar to #724 (comment) it seems these are linting error failing on |
766a256
to
5b009f7
Compare
Now that PR #733 is in, this should pass CI (it does on my fork) and is ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you 💜
…ve classifiers * Add Environment :: WebAssembly to valid PyPI trove classifiers. - c.f. https://discuss.python.org/t/do-we-want-classifiers-for-webassembly-on-pypi/22712
5b009f7
to
4b8ea59
Compare
…ve classifiers (pypa#725) * Add Environment :: WebAssembly to valid PyPI trove classifiers. - c.f. https://discuss.python.org/t/do-we-want-classifiers-for-webassembly-on-pypi/22712 2f685c7
Environment :: WebAssembly
andFramework :: Pydantic
to valid PyPI trove classifiers.This was only very recently added in pypa/trove-classifiers#129.
Closes #727 (duplicate).