Matthias Schoettle

I have a `Dockerfile` that expects `.git` to be present. So I ran into this issue with the git vs path context. Once I found the relevant part in the...

/cc @mxmehl @carmenbianca

True. [PEP 639](https://peps.python.org/pep-0639/) will improve the current situation. The disadvantage of only classifiers is that in the case of BSD it is ambiguous since it maps to multiple possible licenses.

That's basically where this occurred for us. We run dependency scanning in the pipeline (the one from GitLab on GitLab). Besides checking for vulnerable packages/package versions it can also detect...

`setuptools` has support for PEP 639 now (https://github.com/pypa/setuptools/issues/4629). I don't see a pinned `setuptools` version in this repo so it would use the the latest version the next time it...

Thanks! While it looks right, I don't think it works as is: ```shell $ pip show django-forms-dynamic Name: django-forms-dynamic Version: 1.0.1 Summary: Resolve form field arguments dynamically when a form...

> No, running commands like python setup.py sdist directly is deprecated. That's what the `pypi` workflow in this repo uses. Eventually it would be good to convert to `pyproject.toml`.

Unfortunately, the classifiers are ambiguous (or not complete) for some licenses (BSD, Python, Apache). See also here: https://github.com/pypa/trove-classifiers/issues/17. It seems that the classifiers are not taken into account for the...

Waiting for PEP 639 makes sense to me. There is now a feature request for flit: https://github.com/pypa/flit/issues/692

Looks like it. Although it uses the old syntax, not the new one introduced by PEP 639 I think.