Thanks to Luiz Irber for all the pre-work on sourmash, as well as the code reviews on screed; and Brett Cannon for a review of an earlier version of this blog post!
The relevant setuptools docs have been updated to reflect the new toolchain, too!
My takeaway from all of this is:
- configuration files are better than scripts
- a few standard configuration files are better than many
- declarative/static is better than procedural/dynamic
OK! rubs hands with glee let's do this!
"But what do I actually do?"
Brett's post is pretty excellent and was really informative for me, but I have a high tolerance for reading lots of text! It's probably a bit long for people who just want to update their project, though ;).
So I decided to give it a try myself and then post an example!
Recently, I wanted to release a new version of screed, in order to get rid of some DeprecationWarnings for the release of sourmash 4.0. Now, screed is a remarkably ...stable project, by which I mean it does the thing we need it to do and no more, and we're not changing it at all.
BUT. Screed was based on an old school setup.py. So, inspired by Luiz Irber's updating of sourmash to use pyproject.toml, I updated screed similarly. (It was REALLY helpful to have an example!)
pyproject.tomlcan be very close to boilerplate.
- It's basically the three lines that Brett posted...
- the additional stuff for screed has to do with setuptools_scm, which we're using to automatically convert git tags like
v1.0.4into actual version numbers.
setup.cfgbasically contains almost everything your
setup.pycontained, just a bit reformatted to fit into the setup.cfg format.
- your new
setup.pycan now be a really short stub to permit
python setup.py ...to continue to work.
I hope this helps! Comment and ask questions as you have them!
(Also: I just released screed v1.0.5! :tada:)