You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many moons ago in response to not particularly liking the Bazel .runfiles model of laying out dependencies I developed https://git.arrdem.com/arrdem/rules_zapp which attempts to generate more pex-style/vanilla zipapps that directly reflect the intentional sys.path of the packaged artifact.
The original implementation was pretty hacky, and the semantics API has since caught my attention as potentially making it easier for users like myself to recycle large parts of the reference py_binary implementation by just hooking the bits I care about which are what the final output files are and how they're produced.
Obviously it's currently private (and for personal use I'm happy to blithely ignore that) but what's the plan for this particular API and would it be possible to stabilize something like it?
The text was updated successfully, but these errors were encountered:
🔍 Question
Relevant Rules
py_binary
Description
Many moons ago in response to not particularly liking the Bazel
.runfiles
model of laying out dependencies I developed https://git.arrdem.com/arrdem/rules_zapp which attempts to generate more pex-style/vanilla zipapps that directly reflect the intentionalsys.path
of the packaged artifact.The original implementation was pretty hacky, and the
semantics
API has since caught my attention as potentially making it easier for users like myself to recycle large parts of the referencepy_binary
implementation by just hooking the bits I care about which are what the final output files are and how they're produced.Obviously it's currently private (and for personal use I'm happy to blithely ignore that) but what's the plan for this particular API and would it be possible to stabilize something like it?
The text was updated successfully, but these errors were encountered: