Currently, our code relies on the package (ex. pylabcontrol) being the top level package, that is the highest level folder that contains an init file. However, if pylabcontrol is installed in site-packages, there can sometimes be an init file in that folder, which causes issues in the code. We should instead change the package determination code to use a sentinel file that we put in the directory to denote a pylabcontrol package. This will also let us identify available toolboxes on a machine, and could be used to store configuration information.
Currently, our code relies on the package (ex. pylabcontrol) being the top level package, that is the highest level folder that contains an init file. However, if pylabcontrol is installed in site-packages, there can sometimes be an init file in that folder, which causes issues in the code. We should instead change the package determination code to use a sentinel file that we put in the directory to denote a pylabcontrol package. This will also let us identify available toolboxes on a machine, and could be used to store configuration information.