Package py_binary without py_env

[aisbaa]

Hi, yesterday I've tested rules_pyenv and I'm impressed, good job! The only small thing Is that it is a lot harder to package py_birnary target using pkg_tar. Because by default it includes pyenv, which is not what I want. Maybe you have solutions for that? Here's

py_binary(
    name = "py_cli_bin",
    srcs = ["entrypoint.py"],
    main = "entrypoint.py",
    deps = [
        ":cli_lib",
        ":cli_lib_auth",
    ] + cli_requirements,
    python_version = "PY3",
)

pkg_tar(
    name = "py_cli_tar",
    srcs = [
        ":py_cli_bin",
    ],
    include_runfiles = True, # this would include all deps including pyenv
)

I ended up creating source file group and writing simpler version of python bootstrap script to workaround this. Do you know a simple way to include runfiles but exclude pyenv?

---

Update. The method above fails to include include non-python files from cli_requirements. The other thing I tried is bazel build --spawn_strategy=local //cli:/py_cli_tar. It did succeed building tar package, but failed in another target during container_image build.

Related issue: bazelbuild/rules_pkg#135

[ddlees]

@aisbaa Apologies for the delayed response. Were you able to find a way forward for your use case?

For some history, I wrote rules_pyenv to account for rules_python not providing a hermetic and platform aware interpreter out of the box; without any additional configuration rules_python just uses whatever version is installed on the host machine and that makes working in a team particularly inconsistent. At the time I had remote caching/execution setup for CI so it was pretty rare for rules_pyenv to need to download and recompile the interpreter but I can imagine that's a pretty big time suck if you don't have those things configured.

I'll try to allocate some time to figure out how to properly produce a tar artifact using rules_pyenv but I think you may be better off making the switch to something like this --> https://thethoughtfulkoala.com/posts/2020/05/16/bazel-hermetic-python.html

Otherwise, feel free to submit a PR if you're getting impatient. Those are always welcome 😄

[aisbaa]

I parked this issue until rules_pkg version 0.5.0 gets released, which already is, so I should get back to it soon. I wasn't aware of hermetic python, will look into that. Also in bazelbuild/rules_pkg#135 I was suggested to try rules_python/packaging.

Thank you for getting back to this issue!