TL;DR: Yapsy v1.12 has been released with fixes for Python3.6 and multiprocessing on windows.
So, after 3 years
sleeping busy with a fair bit of work and family duties joyful activities, I eventually got some time to actually release Yapsy – the fat-free DIY python plugin management toolkit.
There was a fair bit of contributions (compared to the modest size of the project), that I’m sorry not to have released earlier but which bring some nice polishing to yapsy.
The most prominent news I think is a better compatibility with modern Python (esp. 3.6) and the resolution of a nasty bug that made the instantiation of plugins in their own (sub)processes (with the Multiprocessing Plugin Manager) impossible on Windows (changelog below).
Yapsy – my fat-free DIY python plugin management toolkit — has recently jumped from 1.10 to 1.11 with a great new contribution: allowing plugins to run in their own processes separated from the plugin manager’s (and presumably the application’s) own process.
Adding brand new features is not very frequent for Yapsy (last time was 2 years and a half ago !) but it doesn’t prevent people from using it and contributing to it, which I find really nice.
Besides the features there has been also a fair number of bug fixes contributed which, I guess, can be interpreted as a good sign (even though I’d prefer to have it bug-free).
All of this was the occasion to improve a little more the documentation (also on readthedoc) to be more helpful and make sure that people know how and where to contribute (spoiler: github pull requests are perfectly fine if you’ve lost your sourceforge credentials and don’t intend to get them back ;) )
You can read more on the latest release notes:
We really can’t speak of kaizen for such a small project that only develops from by small strokes twice a year, but to take into account users’ feedback I’ve started trying new tools to improve Yapsy‘s quality and make interactions with users a little smoother:
- for a few months now, the sources (originally in a mercurial repository on sourceforge) have been maintained in sync with a github repository. This should simplify the process of improvement proposals from the contributors, many of whom seem to like github a lot and will now be able to do pull requests.
- since the latest release, yapsy is also linked to the continuous integration service Travis CI so that each new commit triggers a full run of all unit-tests.
Now for those that may be interested the following are my impressions about these tools.