-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
Fails to parse --hash=
values embedded in requirements.txt
#2
Comments
So I removed the
So it did parse all 14 dependencies but treated the |
Is pep-508 able to parse I don't think I saw this in the original pep 508 spec and it would be easy to miss |
This is a better read: https://pip.pypa.io/en/stable/reference/requirements-file-format/#per-requirement-options As hash checking is part of |
Only |
--hash=
values embedded in requirements.txt
Looks like requirements.txt's format isn't equivalent to pep 508, I wonder if it's possible to introduce some sort of flavoring, since pyproject seems to just use pep 508 directly |
Well, your crate is mostly used for parsing from requirements\constrains.txt, pyproject.toml and other spaces where people use PEP-508. And from that set, requirements.txt is the most popular one. Wouldn't you consider solving this supposedly edge case? Maybe there could be an |
Yes, that's why I wanted to introduce some sort of flavoring, possibly having a module for requirements.txt |
That sounds fantastic. |
any updates on this? |
--hash=
values embedded in requirements.txt--hash=
values embedded in requirements.txt
The contents of
requirements.txt
used for parsing: https://github.com/anotherbridge/pdfalyzer/blob/master/requirements.txtWithin the following code: extractor.rs
Here's the
Err
values:I added
lxml
at the end of the file to see if it was a file quirk, and unfortunately not. Is this because it's unsupported in pep-508 crate for now? Wouldn't parsing the text before;
would be a feasible workaround?Your crate is one of the core ones I use [issue originally mentioned at aswinnnn/pyscan#16] and would appreciate it if you could look into it. Thanks.
The text was updated successfully, but these errors were encountered: