Repository navigation
Expose building an archive as an API #36
Description
Activity
hi @moshez !
this would be a welcome contribution, (or I'd be happy to take a crack at it as well). I think stylistically it'd be best to move everything except the click entrypoint out of
cli.pyand into it's own module. I'd suggestbuilder.pybut I'd like to keep that untouched since the logic there is cribbed from zipapp (so I don't want to clutter it), perhapsbuilder.pycould be renamedzipapp.pyand then the archive creation functions could be placed into abuilder.py?No need to CC me, I get all notifications. Oh, and +1!
Sounds good, I should have some time next week to prototype a PR.
Reacted by Loren Carvalho
I have a wrapper for building executables that I would like to move from pex to shiv. However, the API to build executables is not exposed. It seems like starting around the
with Temporary....would be a good place to split up and call an API function.Would that make sense as a PR?