We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Outside of requirements.txt, there are a few other common Python packaging files:
requirements.txt
pyproject.toml
poetry
poetry.lock
pipenv
Pipfile
Pipfile.lock
Each of these functionally boils down to a RequirementsSource, but with a bit of pre-processing to get them out of their dedicated formats.
RequirementsSource
The text was updated successfully, but these errors were encountered:
This was in the original SoW but indicated that it wasn't high in priority, so I'm marking it as potentially follow-on for now.
Sorry, something went wrong.
One slight complication for poetry here is that it currently requires packaging<21.0,>=20.4 whereas we require:
packaging<21.0,>=20.4
https://github.com/trailofbits/pip-audit/blob/cd4dd0825fcff3153d7bcd8ea320dc6f13377f14/setup.py#L32
Let's split this into separate issues for each of these.
Broken out, I turned this issue into a checkbox tracker for each sub-issue.
Closing in favor of subissues, since we don't really need a roadmap-type tracker here.
No branches or pull requests
Outside of
requirements.txt
, there are a few other common Python packaging files:pyproject.toml
(Supportpyproject.toml
#83)poetry
puts locked (i.e., frozen) dependencies inpoetry.lock
(Support Poetry viapoetry.lock
#84)pipenv
usesPipfile
andPipfile.lock
(Supportpipenv
viaPipfile
andPipfile.lock
#85)Each of these functionally boils down to a
RequirementsSource
, but with a bit of pre-processing to get them out of their dedicated formats.The text was updated successfully, but these errors were encountered: