The current behavior of pylinac is to import the gui function from the py_gui.py file. Normally, this is all fine, even if the GUI isn't desired. However, when using pylinac on the web, some build packages complain (Heroku) since tkinter is not available on their stripped-down python build. The solution appears to be to not import the gui functions in the init file. This would mean users have to import/use the gui by calling the submodule (pylinac.py_gui.gui() instead of pylinac.gui()).
The current behavior of pylinac is to import the gui function from the py_gui.py file. Normally, this is all fine, even if the GUI isn't desired. However, when using pylinac on the web, some build packages complain (Heroku) since tkinter is not available on their stripped-down python build. The solution appears to be to not import the gui functions in the init file. This would mean users have to import/use the gui by calling the submodule (pylinac.py_gui.gui() instead of pylinac.gui()).