setPluginPlaces should not presume it was given a list
A fat-free DIY Python plugin management toolkit.
Brought to you by:
tibonihoo
If accidentally instead of a list of paths one provides a single path to setPluginPlaces the map call in locatePlugins will recursively walk from the first character of the path, typically "/" which is not good.
Anonymous
Well, it is expecting a list of enumerable (generator for instance) of paths, so if you provide something else, things go bad indeed, but that's true for any of the methods.
However I get your point, that providing a single string may be tempting and looking (possibly recursively) below "/" is pretty bad.
So I'll add a specific protection against this precise case.
Fix is there:
https://sourceforge.net/p/yapsy/code/ci/f4509587466829bb080a900f5a079ec1f0567d08/
The fix is part of Yapsy1.12