Currently, all function/module imports always need to called with reference to the root folder, e.g., it is necessary to call
from Radiaidd.Backend.Registration import function_abc
which can get a bit messy if these imports are used often and a package name is changed or the package is moved somewhere else. A way to adress this problem generally is to place __init__.py files in the respective submodule folder, that can make functions in subdirectories public so that they can still be imported, even if the module was moved somehwere else.
I think it would be good practice to implement this here. I recently learned how to do this here. With this it should also be possible to move matplotlibwidgetfile.py away from the top level without breaking RadiAIDD^^
Again @schneidorlein ,do you want to try it? See #21 for the "correct" workflow of how to do this.
Again, let me know if you need help!
Currently, all function/module imports always need to called with reference to the root folder, e.g., it is necessary to call
which can get a bit messy if these imports are used often and a package name is changed or the package is moved somewhere else. A way to adress this problem generally is to place
__init__.pyfiles in the respective submodule folder, that can make functions in subdirectories public so that they can still be imported, even if the module was moved somehwere else.I think it would be good practice to implement this here. I recently learned how to do this here. With this it should also be possible to move matplotlibwidgetfile.py away from the top level without breaking RadiAIDD^^
Again @schneidorlein ,do you want to try it? See #21 for the "correct" workflow of how to do this. Again, let me know if you need help!