lp:~thekorn/zeitgeist/zeitgeist-resonance_extensions
- Get this branch:
- bzr branch lp:~thekorn/zeitgeist/zeitgeist-resonance_extensions
Branch merges
- Zeitgeist Framework Team: Pending requested
-
Diff: 385 lines (+276/-23)6 files modified_zeitgeist/engine/extension.py (+82/-0)
_zeitgeist/engine/relevancy_provider.py (+34/-0)
_zeitgeist/engine/resonance_engine.py (+11/-22)
test/resonance-engine-extension-test.py (+39/-0)
test/resonance-engine-test.py (+6/-1)
test/test-engine-extension.rst (+104/-0)
Related bugs
Bug #483556: Make the loading of extensions to the engine configurable | High | Fix Released |
Related blueprints
Branch information
Recent revisions
- 1306. By Markus Korn
-
Changed the way extension methods can be accessed, it is now
engine.extensions. some_method( ) - 1304. By Markus Korn
-
* added license header to the extensions modul
* added some docstrings
* completed doctest for the extension framework - 1302. By Markus Korn
-
* fixed method to unload an extension
* added test/test-engine- extension. rst, a doctest for the extension loader
which is also used to demonstrate how loading and developing extensions
works - 1299. By Markus Korn
-
* use whitespaces in relevancy_
provider. py instead of tabs to keep the diff
as small and readable as possible - 1298. By Markus Korn
-
* added a loader for eninge extensions. for now the only extension we have
(relevany_provider) is disabled by default. The code needs still some work
but works. - 1297. By Markus Korn
-
* fixed engine unittests:
- timestamps are INTEGERS
- raise a KeyError if someone wants to add a duplicate event
* DISABLED the relavncy provider for now, it is broken and needs to be fixed
(https://bugs.edge. launchpad. net/zeitgeist/ +bug/483556 is about making the
loading of this kind of extensions configurable, which is the only
solution here
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)