Skip to content

[FR]: Generate venv at build time #522

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

Open
thesayyn opened this issue Jan 28, 2025 · 2 comments
Open

[FR]: Generate venv at build time #522

thesayyn opened this issue Jan 28, 2025 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@thesayyn
Copy link
Member

What is the current behavior?

This is a tracking issue for all things related to venv generation at build time. Biggest issue so far is when running py_binary put into a docker image on Lambda, it simply does not work since all the paths on Lambda is write protected.

Current issues with venv

#433
#373
#351
#339

Describe the feature

Generate the venv at Build time by making the venv relocatable.

@thesayyn thesayyn added the enhancement New feature or request label Jan 28, 2025
@thesayyn
Copy link
Member Author

Blocker: #339 (comment)

@vinnybod
Copy link
Contributor

vinnybod commented Feb 6, 2025

I think I am blocked on this.

I am trying to create a python environment on an OCI image that has a few dependencies pre-installed. It doesn't seem possible to have the venv already created in the image. It also doesn't seem possible to symlink the venv in the $PATH and still contain the 3rd party dependencies.

https://github.com/vinnybod/bazel-examples/tree/python-oci/python-oci

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

No branches or pull requests

3 participants