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

Support for Pipenv #342

Open
vpavlin opened this issue Nov 19, 2020 · 3 comments
Open

Support for Pipenv #342

vpavlin opened this issue Nov 19, 2020 · 3 comments

Comments

@vpavlin
Copy link

vpavlin commented Nov 19, 2020

We are looking at using cachito in our image builds and it seems like it only supports pip and requirements.txt dependency definition. Is there a plan to add support for Pipenv (Micropipenv) and Pipfile/Pipfile.lock tooling?

@fridex
Copy link

fridex commented Nov 19, 2020

+1, it would be great to add support for Pipenv files (Pipenv is now under Python Packaging Association). micropipenv (a lightweight wrapper for pip to support also Pipenv files) can serve as an alternative - https://github.com/thoth-station/micropipenv The main issue with raw requirements.txt is reproducibility when requirements.txt many times do not state all the packages with digests (to check provenance and integrity of software installed).

micropipenv is also available in s2i container images that run Python 3.

@lcarva
Copy link
Contributor

lcarva commented Nov 20, 2020

I agree! IMO it makes perfect sense to have this support in Cachito. If you're interested in contributing, I suggest starting by writing up an initial design describing how this can be achieved. Unfortunately, we don't have a concise guide on how to start. If it helps, the fetch_pip_source function is the entry point for processing a repo that uses the pip package manager.

@fridex
Copy link

fridex commented Dec 3, 2020

Looking into sources, it looks like a major module rewrite as many parts are shared with micropipenv.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants