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
Being able to pass arguments to bork build to override zipapp configuration would be very nice, especially for testing/debugging if a zipapp of a project can be built.
I'm thinking:
--zipapp [true|false] If true, build a zipapp. Otherwise, don't build a zipapp.
--zipapp-name NAME NAME is the name of the project, as used in the ZipApp filename.
--zipapp-main ENTRYPOINT ENTRYPOINT is of the format "some.module:function_name". Implies `--zipapp true`.
This means if you want to test a zipapp build, you can just do (e.g.) bork build --name fido --zipapp-main fido.fido:main
The text was updated successfully, but these errors were encountered:
I downloaded the latest release, and made very few changes and was able to make a zipapp of it.
First, I added a pyproject.toml with these contents:
[tool.bork.zipapp]
enabled = true
main = "fido.fido:main"
And added this at the start of their setup.cfg:
[metadata]
name=fido
If what I suggested above, or an equivalent, is implemented, this can be done with bork build --zipapp-name fido --zipapp-main fido.fido:mainand no code changes from what they already have.
Being able to pass arguments to
bork build
to override zipapp configuration would be very nice, especially for testing/debugging if a zipapp of a project can be built.I'm thinking:
This means if you want to test a zipapp build, you can just do (e.g.)
bork build --name fido --zipapp-main fido.fido:main
The text was updated successfully, but these errors were encountered: