| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
add a MODULE.list_methods that returns a list of all the methods for
a module
note that these kind of crisscross system.listMethods, but tis
okay
|
|
|
|
|
|
|
|
|
|
|
| |
update modules that need new location
modules/func_module.py: update to use new logger/config locations,
also go ahead and register as a real module, to shut up the
start up. It shouldn't hurt anything
Some minor import reordering at a couple places (I try to keep
at least system import alphabetical)
|
| |
|
| |
|
|
|
|
|
|
|
| |
mostly just removing unused modules
change "from codes import *" to "import codes" in a couple
places and updated accordingly
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
add "module_version", "module_api_version" and "module_description" as
base object methods. All classes based on func_module should get this.
modules should set a self.version, self.api_version, self.description
with approriate values. class or instance variables both work. If
values aren't set, defaults are provided.
alternativelt, the modules can implement and export "module_version",
"module_api_version", and "module_description" themself if they
like
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also implies that methods calls need a module as well
(aka, you now have to call test.test_add instead of just test_add)
but this also means you can setup
modules/foo/bar/blip.py
and blip.py exports a "do_blippy" method, which you would call
by the name
foo.bar.blip.do_blippy()
Note, any subdir that has module files in it, will need an
approriate __init__.py file.
server.py, func_module.py: To do the above, we need to pass
in the module_name to the register function, so we can associate
it correctly.
server.py also got a fix for a FuncException that needed
tobe codes.FuncException
|
|
|