2014-06-19, 15:02
Hi,
Recently I've had users complaining of issues with an addon I develop, which I ended up tracking down to conflicts between the module included in the resources/lib directory and another module installed on their system as a xbmc library/script. Now these are usually conflicts with modules that I haven't specified in the addon.xml file, but it seems they're still included in the python module lookup path. Is that the correct behaviour? I would have thought that I should only get the modules that I've declared in my addon.xml included. What do others do about this to avoid conflicts, do they usually rename their bundled dependencies or ensure when they modify the python path that the folders they add are added at the start rather than the end?
Thanks,
Adam
Recently I've had users complaining of issues with an addon I develop, which I ended up tracking down to conflicts between the module included in the resources/lib directory and another module installed on their system as a xbmc library/script. Now these are usually conflicts with modules that I haven't specified in the addon.xml file, but it seems they're still included in the python module lookup path. Is that the correct behaviour? I would have thought that I should only get the modules that I've declared in my addon.xml included. What do others do about this to avoid conflicts, do they usually rename their bundled dependencies or ensure when they modify the python path that the folders they add are added at the start rather than the end?
Thanks,
Adam