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.
Recently while working on yapsy, I fell on a few subtleties related to the creation of Python packages.
I use distutils obviously and the generated packages are uploaded on http://pypi.python.org, but I was struggling with the following problems:
- the data files used by my unit-tests were not packaged
- I couldn’t get pypi to understand that one of the source package was for Python2 installations while the other was for Python3 so that only one of them was displayed on the package page, and of course the few users yapsy has kept complaining that the code didn’t work for obvious reasons like importing ‘configparser’ whereas this module is spelled ‘ConfigParser’ in Python2
The solutions to both problems now seem obvious to me, but were strangely difficult to come across on the web.
Another release of yapsy, my little do-it-yourself plugin library, just before the end of the year, and maybe also the end of the world ;)
This year has brought even more ideas and important features to yapsy via user contributions and stackoverflow questions than previously.
The details of all changes can be found in the release note on sourceforge, but I’d like here to give again all my thanks to this year’s main contributors:
- Mathieu Havel
- Mathieu Clabaut
- Mark Fickett
I’m also proud to say that this year, yapsy has been adopted by the following renown project:
- Nikola, the static blog generator that I heard of on planet Python long before being contacted by its author about yapsy
- err chatbot who has had its own FLOSS Weekly episode not so long ago
A more complete list of project using yapsy is available on the online documentation.
Seeing this small piece of code being adopted by other projects in the wild is a great motivation to maintain it and to make sure it is still relevant !
A new version of Yapsy, my fat-free DIY plugin framework, has just been released ! The project went (again) dormant for a bit more than one year during which a couple of bug reports and features requests eventually waked it up :)
More details on the new release are available on sourceforge and so are the downloadable files.
And the first big news is that there is a version compatible with Python3 at last !
Another big news is that this gave me the occasion to search a bit over the internet and realise that there are actually people talking about yapsy here and there.
You find traces of it already on the famous stackoverflow (yes as far as I can tell, and as of 2011/12 they are all mentions of ‘my’ yapsy, very moving indeed :) ), on this quick inventory of Python plugin systems and more anecdotally on pastebin
And for the specific projects that use this library, so far I’ve found:
And of course this adds up with the great people I already had the occasion to thank in my latest post about yapsy.
Let’s face it, this ridiculously small piece of code is h-y-p-e… (ok I may be overdoing it a little but if I don’t do it who will ?)
I’ve just received a nice e-mail pointing at an even nicer blog post about one of my pet project: Yapsy and the author states it quite clearly: “Yapsy is awesome”!
Many thanks to Roberto Alsina for these kind words and for the very nice tutorial he wrote about yapsy.
To be honest, Yapsy is above all just an absurdly tiny piece of code, and , even with that, still has a long way to go before I dare qualify it as awesome, but one thing is sure the developpers who use it already are undoubtedly the awesome ones !
Yapsy is a project I started 3 years ago on my free time, and put on SourceForge “just in case” it could be helpful… It went dormant several times but was waken up by requests and suggestions sent by developpers like Peppy’s Rob McMullen, MysteryMachine’s Roger Gammans and now Aranduka’s Roberto Alsina who all deserve a big thank you.
In its latest release (5 days ago) I corrected some bugs and tried to make the documentation as useful as possible. All in all, I wanted to highlight the ways in wich yapsy could be used to simplify the development of a plugin manager, but Roberto beat me to this. I’m especially proud of two of his comments:
- “One of the great things about Yapsy is that it doesn’t specify too much.”
- “it helps you write better code.”
The first one was clearly indented but also known to be hard to get right (and IMHO yapsy’s not quite there yet).
The second is way beyond yapsy’s initial scope, but it’s really sweet to read, especially from somebody who — as it seems — has already tasted Qt development
More info about Yapsy at ohloh