Could you make a release of Yapsy 2.0
Development moving to github.
Use github actions for automatic tests.
Bump major version to drop Python2 support.
Also ignore files generated by direnv.
Plugin Superclass loaded instead of the plugin itself
deprecation warning for imp
meaningless traceback spam loadPlugins function
Yapsy-loaded Python modules have incorrect encoding
Issues while using async
Added tag release_Yapsy-1.12.2 for changeset 851e4edcf10e
Add config file and badge for readthedocs
New release?
Just released Yapsy with your fix: https://pypi.org/project/Yapsy/1.12.2/ Thanks again for your contribution !
directories_list in PluginManager is not respected
The fix was in Yapsy-1.12
setPluginPlaces should not presume it was given a list
The fix is part of Yapsy1.12
Multiprocess Plugin fails under Windows 7
This was fixed in Yapsy 1.12 release.
Test cases are not passing in current version (1.11.223)
I haven't heard of the pb coming back since the fix mentionned above, so closing this ticket.
Please make a new release
At least 2 releases have been done since the request I believe, so closing this ticket.
Updated list of contributors
Prepare new release
Fix more doc warnings
Fix sphinx warnings with correct note/warnings format
Improve package upload script
Improve doc generation scripts for releases
Ignore extra files
Bump minor version
New release?
No test on Python3.7 as travis is not supporting it yet
Push New Version to PyPI
Sorry for not replying directly and thanks for your interest in yapsy. A release has actually been done last september (so after both comments). Hope you could get what you needed in it !
Pull request made on github
Hello, Thanks for your pull request and for coming all the way to here to push it even more. Indeed I saw it a little while back but didn't get the time to process it. This is now done (and yes, you're right about the error with Python2.6 and unelated to your change). Thanks again, and sorry for not being more responsive !
Commit adds code to use importlib, if available
stop testing against 2.6, start with 3.7
Commit adds code to use importlib, if available
Pull request made on github
Skip evaluating dunder methods when checking plugin subclasses
Add recent changes to changelog
Stop pushing doc to pypi
Update copyright year
Removed tag release_Yapsy-1.12.023
Use twine to upload to the new pypi
Removed tag release_Yapsy-1.12.0
Added tag release_Yapsy-1.12.0 for changeset c1566d5c5fb4
Use normalized and simpler pqtch version.
Added tag release_Yapsy-1.12.0 for changeset cda16532447d
Bump *appropriately* the version :)
Added tag release_Yapsy-1.12.023 for changeset 2e9f7c40b531
Bump version for next release
Update list of contributors
Revert addition of python 3.7 tests (not supported by travis yet)
Remove obsolete download badge.
Ask for tests on Python 3.7
Test cases are not passing in current version (1.11.223)
Here is the fix (which I hope, is cross-platform enough, we'll see with the CI): https://sourceforge.net/p/yapsy/code/ci/0f24c72014ebc79beb812fbaefc15e4edd3f50d4/
Make the test more robust to "unusual" unpacking of the module.
Hello, thanks and also... sorry if that didn't work in your case. I'm not a heavy user of Cython to say the least, so I may be mistaken but it seems Cython modules don't get imported that easily (at least not without a specific set-up), right ? (again I'm not so familiar, please forgive me if I'm wrong). To me importing Cython module may motivate wirting a new PluginLocator (see doc at https://yapsy.readthedocs.io/en/latest/PluginFileLocator.html) Or if you're sure it's enough adding some customisation...
Please make a new release
setCategoriesFilter not compatible with Python 2.7 [Owner edit: it is !]
Sorry, but I don't get your point here. copy is a method of dict in Python2.7 and 3.x as far as I can see in the doc, here for Python2.7: https://docs.python.org/2/library/stdtypes.html?highlight=dict#dict.copy this method is unit-tested and the tests pass ok for for Python2.7 on travisCI: https://travis-ci.org/tibonihoo/yapsy/jobs/351908101
Sorry, but I don't get your point here. copy is a method of dict in Python2.7 and 3.x as far as I can see in the doc. this method is unit-tested and the tests pass ok for for Python2.7 on travisCI: https://travis-ci.org/tibonihoo/yapsy/jobs/351908101
setPluginPlaces should not presume it was given a list
Fix is there: https://sourceforge.net/p/yapsy/code/ci/f4509587466829bb080a900f5a079ec1f0567d08/
Protect against providing a single string to setPluginPlaces
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.
directories_list in PluginManager is not respected
Fixed with https://sourceforge.net/p/yapsy/code/ci/7b632977e7bda49f6dcdac83a85439021df8b3ab/ (including a shameful typo in the commit mesage: Encore => Enforce ....)
Encore the exact directory list provided at construction time.
directories_list in PluginManager is not respected
Indeed that's unfortunate and unexpected. A fix is underway.
Ack!. Sorry for not releasing ealrier, I'll do my best to get this done this week. (and thanks for maintaining this module in debian btw !)
Please make a new release
setPluginPlaces should not presume it was given a list
PluginManager.collectPlugins should return value from loadPlugins
setCategoriesFilter not compatible with Python 2.7
Import errors when plugin attempts to use multiprocessing.Pool
Hello, Sorry for the wait but I think I nailed the root cause of your problem. Basically, you're on windows and on windows the child process shares no memory with the parent process. Which means in particular that it won't know anything about the plugin's module that has been loaded (with the "yapsy_loaded_plugin_multiprocess_plugin_0" name typically) in the PluginManager.py This is by design both on yapsy's side and on the multiprocessing+windows side, so the only way to solve that is by handling...
Multiprocess Plugin fails under Windows 7
This problem is fixed with the following commit: https://sourceforge.net/p/yapsy/code/ci/abbdb0c4b86220b39230c8182358117495bbc00a/ The root cause was that on Windows the child process doesn't share any memory with the parent process and typically forget what has been imported with imp. in the PluginManager. As a consequence, to make it work the plugin candidate's module has to be imported a second time in the child process. Not terribly elegant but seems to work and make sense.
Fix tests failures on Windows, due to path separator diffs.
Fix tests failing on windows because symlink are not supported.
Make multiprocess plugin work on windows too !
directories_list in PluginManager is not respected
Does not support Cythonized modules
Push New Version to PyPI
Import errors when plugin attempts to use multiprocessing.Pool
fix radomness
fix dict access for python3
fix indentation
fix indent and add a little more tests
add a filter-based getter selecting plugins on ...
fix deprecation warning for the logging api