Shantanu
Shantanu
I think this PR should be good and would solve a problem in a codebase I work on! https://github.com/astral-sh/uv/issues/8492 is a feature request against uv for them to do this...
That makes sense and is basically right! For your users, a simple `numpy>=1.24` is sufficient. `magika` doesn't rely on any newer numpy APIs, so if a user (and their package...
Check MANIFEST.in could also be nice! https://github.com/mgedmin/check-manifest
PR welcome. IIRC isinstance on old-style unions is only supported on 3.10 and newer
If we need to be really conservative about a new metadata version, can we revert whatever it is that is putting License-File into 2.1 metadata, since PyPI hard rejects that?...
My user story: - At some point I added `license = {file = "LICENSE"}` to some project. I think I got this from packaging.python.org - Later, I try to upload...
Thanks for explaining that! Yeah, I ended up just using twine (before I saw your post and konstin's post [here](https://github.com/astral-sh/uv/issues/9513#issuecomment-2547787109) explaining that PyPI validates formdata, not the uploaded METADATA)... so...
Similar to https://github.com/astral-sh/uv/issues/1495#issuecomment-1950442191 , you can symlink to solve this. ``` uv venv /app/.venv ln -sf /app/.venv .venv uv sync ```
If you want like 90% of the benefits of a lock file in a PEP 723 script in a way that is also extremely concise, you can use https://docs.astral.sh/uv/guides/scripts/#improving-reproducibility
(note that you can get behaviour 1 by passing `--skip-magic-trailing-comma`/`-C` )