Bork v7.0.0 & v7.0.1 Releases

Bork v7.0.0 & v7.0.1 have been released!

Bork is a build and release frontend for Python projects configured using pyproject.toml.

v7.0.1 was entirely to address problems with the v7.0.0 release, so I am just treating them as one release. More details can be found in the release notes on GitHub.

Documentation

There’s actual good documentation now! You can find the documentation at bork.readthedocs.io.

Breaking Changes

There were two major breaking changes with this release:

Switching from Click to argparse.
Removing bork dependencies and bork.api.dependencies().

Click requires manually managing the LC_ALL/LANG environment variables, and I’ve been told by multiple people that it made adopting Bork more difficult.

bork dependencies and bork.api.dependencies() were implemented using the pep517 library. That library is deprecated, and I couldn’t find a way to get equivalent functionality. Between that and bork dependencies having already been broken for multiple releases without anyone noticing or mentioning it, I decided to remove it. I’m not opposed to it being re-added later, if someone figures out how to do so.

Old Bork versions & Rust

bork release uses Twine behind the scenes. Twine relies on the readme-renderer library. With readme-renderer v42.0, it changed dependencies to one that requires Rust. This meant installing Bork would require a Rust compiler, even though none of the related functionality is used.

For now, I have pinned readme-renderer to below v42.0. Long-term, I am unsure of how to approach this. Bork may need its own code for uploading to PyPi.

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 (the AT smallest DOT dog).