-
Notifications
You must be signed in to change notification settings - Fork 16
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
Feature Request: parse_pipfile
function
#47
Comments
Hi @malikoth, thanks for the feature request. The purpose of this package to providing a drop-in replacement for existing uses of I think if If you just want to be able to parse a |
Fair enough. I'd been thinking that That being said, the
In that hypothetical eventual future, maybe we will be adding this in the future. :) |
Yep! I expect |
Or feel free to close, and reopen when / if appropriate. |
With adoption increasing for
Pipfile
based dependency declaration, it would be great if this library could parse aPipfile
as well. Nice thing is that since aPipfile
doesn't support nested files likerequirements.txt
does, and the format of the file is just TOML, it should be a fairly short function that just reuses a lot of the existing functionality.If this seems reasonable scope for this project, I'll happily submit a PR with it. :)
The text was updated successfully, but these errors were encountered: