You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the interest of addressing some issues/ideas that have risen up in the past couple weeks, mainly:
structuring the project in an organized and logical way to encourage contributions and development from Olin students with a variety of programming/Python experience
It seems that we've reached the comfortable limit of a flat project structure - I recently rearranged the project files in #44 based on the guidelines from The Hitchhiker's Guide to Python. Looking at the Olin API's folder structure, I think that splitting up document_models.py and resource_models.py would be a nice first step. After that helpers.py needs to be pulled apart and reorganized - I'm still not sure what the best way to structure it would be.
Some resources to help with Flask, sockets, and celery along the way:
Breaking up helpers.py into multiple helper functions is taken care of with #71
Greater restructuring with implementing document and resource model folders was taken care of with #68
In the interest of addressing some issues/ideas that have risen up in the past couple weeks, mainly:
It seems that we've reached the comfortable limit of a flat project structure - I recently rearranged the project files in #44 based on the guidelines from The Hitchhiker's Guide to Python. Looking at the Olin API's folder structure, I think that splitting up
document_models.py
andresource_models.py
would be a nice first step. After thathelpers.py
needs to be pulled apart and reorganized - I'm still not sure what the best way to structure it would be.Some resources to help with Flask, sockets, and celery along the way:
I'm proposing a project structure similar to this:
The text was updated successfully, but these errors were encountered: