Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Mass change: import logging -> from logging import getLogger | Jan Pokorný | 2015-01-09 | 1 | -3/+2 |
| | | | | Signed-off-by: Jan Pokorný <jpokorny@redhat.com> | ||||
* | command: make usable as a library (output as a string, etc.) | Jan Pokorný | 2014-09-01 | 1 | -2/+12 |
| | | | | | | New unit test included. Signed-off-by: Jan Pokorný <jpokorny@redhat.com> | ||||
* | plugin_registry vs. protocol(s): "kludge" -> fixed feature | Jan Pokorný | 2014-09-01 | 1 | -0/+2 |
| | | | | | | | | | | | | | | | | | | In fact, commit 8dd14ec29fe829e9edf0102e45966a4a1cc012d7 commented out what was intentionally present to prevent RuntimeWarning due to importing discovered plugins to the yet non-existent module namespace (missing parent) in case the respective registry hadn't been imported in advance. That commit tried to solve a conflict with protol.py, which referred to "clufter.plugins" module namespace, but unlike the previous registries (formats, filters, commands), "plugins" is not backed by a real module (i.e., neither plugins.py nor plugins/__init__.py exist at the top level). Solution is simple, make protocols registry set the namespace as a non-value, which is then considered a signal not to attempt any such for-the-sake-of-sanity complementary import. Signed-off-by: Jan Pokorný <jpokorny@redhat.com> | ||||
* | (Optionally) promote protocols to first-class entity | Jan Pokorný | 2014-08-29 | 1 | -0/+41 |
+ reflect that on the formats' level (also bring a convention for that) + make plugin_registry.probe fnc more tolerant towards non-classes as we want to differentiate between protocol on instance basis rather than based on dedicated classes (because we want to pragmatically maintain interchangeability with plain strings!) + make extra steps in protocol.py so the mentioned interchangeability actually works Signed-off-by: Jan Pokorný <jpokorny@redhat.com> |