2010-10-18, 05:48
The Python Bindings are now to the point where they support everything required. They interface mythicalLibrarian with a named mkfifo pipe which is fully POSIX compliant. The DBPin option is now supported for those who use a DBPin. There should be no problems with the python bindings at this time.
In order to reach full maturity, the Python Bindings requires a test routine much like mythicalLibrarian's --mythicalDiagnostics.
mythicalLibrarian itself is fully supporting the python bindings in their current state. some changes will be required for full fledged diagnostics.
mythicalSetup requires addition of python bindings options and dependencies checking. Until I write mythicalSetup to merge python bindings into mythicalLibrarian, the directions on the previous page are still the preferred ones for use with MythTV v0.24.
When mythicalPythonBindings.py is passed a filename, it pulls all information out of the MythTV database about that file, including commercial skip information. I feel that the title "mythicalPythonBindings.py" is a bit too long and underdescriptive. Will someone recommend a new name to me? I'm open for anything.
In order to reach full maturity, the Python Bindings requires a test routine much like mythicalLibrarian's --mythicalDiagnostics.
mythicalLibrarian itself is fully supporting the python bindings in their current state. some changes will be required for full fledged diagnostics.
mythicalSetup requires addition of python bindings options and dependencies checking. Until I write mythicalSetup to merge python bindings into mythicalLibrarian, the directions on the previous page are still the preferred ones for use with MythTV v0.24.
When mythicalPythonBindings.py is passed a filename, it pulls all information out of the MythTV database about that file, including commercial skip information. I feel that the title "mythicalPythonBindings.py" is a bit too long and underdescriptive. Will someone recommend a new name to me? I'm open for anything.