#No License for Litestar-htmx on pypi

1 messages · Page 1 of 1 (latest)

misty ermine
#

Hi, In my company I migrated our repo from FastAPI to Litestar .. so far things are great. We procure the lib and host in private repo. One issue I am facing recently is that the procurement of new versions fails with reason "No Valid License" , turns out the dependency (https://pypi.org/project/litestar-htmx/) doesn't have a license on PYPI. I felt asking here is better than creating an issue.

gray shaleBOT
#
Notes for No License for Litestar-htmx on pypi
At your assistance

@misty ermine

No Response?

If no response in a reasonable time, ping @Member.

Closing

To close, type !solve or byte solve.

MCVE

Please include an MCVE so that we can reproduce your issue locally.

lyric lichen
#

this should be resolved

#

with version v0.4.0 there is a license file now

#

this is the pinned version in the next release of Litestar

misty ermine
hidden oarBOT
# misty ermine Thanks, But I still don't see license on the Pypi meta https://pypi.org/project...

Description

  • Added License to pyproject.toml so that It comes on pypi
  • Also added few classifiers which seem okay from the main Litestar repo

Closes

Summary by Sourcery

Add license and classifiers to pyproject.toml to enhance project metadata for PyPI.

Build:

  • Add license information to pyproject.toml to ensure it appears on PyPI.
  • Include additional classifiers in pyproject.toml to better describe the project.
lyric lichen
#

oh, I haven't updated the pypi meta. However, you should see the license file in the wheel now. I'll take a look at your PR and merge

#

i'll have to do another point release to make pypi update htough

misty ermine
#

yeah yeah , the procurement process in my company checks the metadata I think, not the wheel file hence the no valid license message. Thanks for the quick reply

lyric lichen
#

ok, give me just a few and i'll have a new patch out

misty ermine
#

damn that was fast-af .. respect++
thanks a lot

lyric lichen
#

i think you should be good to go now

#

let me know if that doesn't cover what you need though

#

i'll clean up the readme a bit more, but hopefully this gets through your procurement checks

#

let me know if you hit any other packages with issues.