xbmc
[service.cronxbmc] 0.1.6
Description
This is an addon I've maintained for years but never submitted to the official repo before, hence the reference to xbmc in the addon id. I've removed all other references and renamed to them to Kodi but kept the addon id name for compatibility purposes.
This addon add a basic cron scheduler for recurring tasks. These can be scheduled via a GUI using built in functions or JSON calls. It can also be imported as a dependency within another addon and used to schedule tasks so other addons don't need to create their own schedulers. Syntax for that can be found in the documentation.
Checklist:
- [x] My code follows the add-on rules and piracy stance of this project.
- [x] I have read the CONTRIBUTING document
- [x] Each add-on submission should be a single commit with using the following style: [script.foo.bar] 1.0.0
Additional information :
- Submitting your add-on to this specific branch makes it available to any Kodi version equal or higher than the branch name with the applicable Kodi dependencies limits.
- add-on development wiki page.
- Kodi pydocs provide information about the Python API
- PEP8 codingstyle which is considered best practise but not mandatory.
- This add-on repository has automated code guideline check which could help you improve your coding. You can find the results of these check at Codacy. You can create your own account as well to continuously monitor your python coding before submitting to repo.
- Development questions can be asked in the add-on development section on the Kodi forum.
I think everything is fixed up with the exception of the one @TermeHansen commented on above. The import into other addons doesn't seem to work without it. Is there a better way to make sure the required files are in the path?
I think everything is fixed up with the exception of the one @TermeHansen commented on above. The import into other addons doesn't seem to work without it. Is there a better way to make sure the required files are in the path?
I looked at pandas last night and it should be possible to do with __init__.py file without adding to path. I'll try tonight and let you know.
edit made a PR for a fix for this
Updated with some fixes for the relative imports. There is still an __init__.py file but it facilitates the use of this addon within others as an import.