BREAKING BORK CHANGES – Bork v9.0.0 Release
Bork v9.0.0 has been released, and there are HUGE changes!
Bork is a build and release frontend for Python projects configured using pyproject.toml.
The specific changes included in this release can be found in the release notes on GitHub.
BREAKING CHANGES
Bork no longer uses Twine for uploading releases to PyPi. In its place, a custom PyPi uploader was implemented using urllib3.
If you use bork release, you should make sure to define the environment
variables BORK_PYPI_USERNAME and BORK_PYPI_PASSWORD. These are
equivalent to the previously-used TWINE_USERNAME and TWINE_PASSWORD,
but specific to Bork.
If there are features you used before but can’t use now, please open an issue on GitHub.
New Feature: ZipApp configuration from the command line
Bork now supports the following flags, which override what is defined in pyproject.toml:
--zipapp: Always build a ZipApp.--no-zipapp: Never build a ZipApp.--zipapp-main: Specify the ZipApp entrypoint.
This allows you to clone any PEP 517-compliant
project (that is, one using pyproject.toml) and build a ZipApp with the
following command:
bork build --zipapp --zipapp-main $ENTRYPOINT
Notably, since Bork provides graceful fallback for setuptools (setup.py/setup.cfg)
based projects, this means you can run the same command to generate
ZipApps for them, as well.
Other Changes
The other changes were related to CI and minor refactoring.
Contact Info
If you run into problems, please open an issue on GitHub.
If you’re using Bork, please reach out and let me know what you’re using it for and what you think of it! I don’t know much about who uses Bork, and I would love to have more insight into what people feel works well and what could be better.
You can contact me on Mastodon (@puppy@weirder.earth) or via email (ellen AT duckinator DOT net).