Michael J Gruber <[email protected]> writes: > Hi there, > > Maybe 0.40 would be a good candidate for "going split config", unless > there are pressing matters for a release. By that I mean that
In fact I want to release 0.40 before introducing some potentially breaking things, so that that iterator fixes can get to the people that need them. I almost called 0.40 a point release (0.39.1), but it seemed weird to introduce new API functions in a point release. > - the default setup offers - or chooses by default - an XDG setup This requires someone (TM) to update the code and the test suite. I'm currently dealing with a backlog of patch review, so it probably won't be me, at least not immediately. > - doc is consistent with that > - split setup actually works ;-) > - all bindings support it. > Specifically, I'm not sure the python bindings do - maybe it's just > some users such as alot or afew which do not yet, or I failed to set > them up (or teach them) correctly. There are a couple of split config python tests T055-path-config, so it should work at some level. There is a new (compared to the old bindings) keyword argument 'config' to database constructor, but the default CONFIG.SEARCH should work for XDG layout (unless multiple configurations exist, perhaps). > Also, `setuptools` is deprecated, so it would be worth switching to > pip for building and installing a wheel, or other modern build tools. I have looked at this a few times, but I got stuck with the fact that our setup.py reads several things from the parent build, including the version, and the generated module _notmuch_config.py. Maybe if we write the version into _notmuch_config.py, a more declarative approach can work. Anyway, the TL;DR is that any of these tasks would delay the release. I mean, everything always takes longer than planned, and weird things come up (currently I discovered gdb doesn't work at all on debian/armhf). So additional last minute "stretch goals" don't really work for me. _______________________________________________ notmuch mailing list -- [email protected] To unsubscribe send an email to [email protected]
