Closed MarkRx closed 2 years ago
I think this is an undesirable solution - think of it as a workaround.
I suspect what is going on is the dependent packages have not been updated since natlink moved to qualified imports. I think the issue should be reported in caster or other dependent packages.
Well, from the new version of natlink, the import should go different:
from natlinkcore import natlink
Please try, and remove the set PYTHONPATH line above...
Closing as this is being addressed in dragonfly
In order for dragonfly to import natlink when running the Run_Caster_DNS.bat script it needs to be directly accessible. I think this can be done by putting it on the python path using a module.pth file in the natlink python module.
https://docs.python.org/3/library/site.html
Without the module on the path it fails with this:
The path can also manually be modified by setting the PYTHONPATH variable: