packaging
packaging copied to clipboard
pypa
Core utilities for Python packages
Hi there! First of all, thanks for continuing to maintain this package -- it's extremely useful 🙂 I'm one of the maintainers of [`pip-audit`](https://github.com/trailofbits/pip-audit), and we had a user report...
Since we require PRs to be synced to 'main', does running on push actually give us any benefit? As long as we don't cheat with admin privileges, I would think...
Now that we're on Python 3.7+, this is a theoretical option we have. Should we? The main arguments "for" that I can come up with, are basically all the arguments...
Similarly to #610, the following logic could be exposed as public API. https://github.com/pypa/packaging/blob/606c71acce93d04e778cdbdea16231b36d6b870f/packaging/tags.py#L501-L506
> I'm good with this -- I'd like to revisit what files we put in our sdist in a follow up though. :) _Originally posted by @pradyunsg in https://github.com/pypa/packaging/issues/546#issuecomment-1271652501_
Closes #408
Is there interest in a pull request for functions that perform the inverse operation of ```packaging.utils.parse_wheel_filename``` and ```parse_sdist_filename```? It seems like an omission that there is no function such that...
users of setuptools_scm like to expose their version variables, unfortunately importing Version, loading it to compile the regex and parsing the version string is often a cost they don't want...
Closes: #469. * Fix validation of the given `version` in the `packaging.version.Version`'s constructor. * Fix validation of the given `spec` in the `packaging.specifiers.Specifier`'s constructor. * Complement relevant tests, including adding...
I'm looking to migrate a caller from utilizing `distlib.wheel` to instead use `packaging.utils.parse_wheel_filename` and my tests encountered an edge case which isn't handled by the `packaging` version here's the distlib...
