The __init__.py file has a lot going on. The __init__.py should generally just contain the necessary code to make imports work as you expect/want them to, and not have a lot of other definitions. One part of OMW's __init__.py that can be easily moved out is the URL routes, and the standard place to put them is in a views.py file. At some point we may want to create Flask blueprints for the various facets of OMW (e.g., one for queries, one for authentication, one for upload and validation, etc.), but for now we can just put them in a single module.
The
__init__.pyfile has a lot going on. The__init__.pyshould generally just contain the necessary code to make imports work as you expect/want them to, and not have a lot of other definitions. One part of OMW's__init__.pythat can be easily moved out is the URL routes, and the standard place to put them is in aviews.pyfile. At some point we may want to create Flask blueprints for the various facets of OMW (e.g., one for queries, one for authentication, one for upload and validation, etc.), but for now we can just put them in a single module.