Skip to content
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

Split Pipfile parsing to independent library #967

Closed
gsemet opened this issue Oct 24, 2017 · 2 comments
Closed

Split Pipfile parsing to independent library #967

gsemet opened this issue Oct 24, 2017 · 2 comments
Labels
Type: Discussion This issue is open for discussion. Type: Enhancement 💡 This is a feature or enhancement request.

Comments

@gsemet
Copy link
Contributor

gsemet commented Oct 24, 2017

Reference: #952.

Parsing à Pipfile using pipenv adds many dependencies (ex: flake8.cli).

Is it possible to split the parsing part from the pipenv CLI into a different package?

I would like to contribute to at least ReadTheDocs and PBR to help them support Pipfile, and that would help a lot if everyone use the same parser.

@erinxocon erinxocon added Type: Discussion This issue is open for discussion. Type: Enhancement 💡 This is a feature or enhancement request. labels Oct 24, 2017
@techalchemy
Copy link
Member

This seems like a good idea, although technically Pipfile parsing is handled by Toml via the Pipfile spec (see pypa/pipfile)

@erinxocon
Copy link
Contributor

@stibbons @techalchemy That repo will eventually contain a parser for Pipfiles once the pipfile spec settles a little. Probably extract it from pipenv.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Discussion This issue is open for discussion. Type: Enhancement 💡 This is a feature or enhancement request.
Projects
None yet
Development

No branches or pull requests

3 participants