I was referred here by StackOverflow, but the wiki page disappeared, so here is a new one.
parent
e4604946f6
commit
700be245fd
1 changed files with 22 additions and 0 deletions
22
Large-app-how-to.rest
Normal file
22
Large-app-how-to.rest
Normal file
|
|
@ -0,0 +1,22 @@
|
|||
"Official" Advice
|
||||
-----------------
|
||||
`packages <http://flask.pocoo.org/docs/0.10/patterns/packages/>`_
|
||||
`blueprints <http://flask.pocoo.org/docs/0.10/blueprints/>`_
|
||||
|
||||
|
||||
|
||||
How does Django do it?
|
||||
----------------------
|
||||
::
|
||||
INSTALLED_APPS = (
|
||||
)
|
||||
|
||||
Django avoids the circular import by using a different routing system (non-decorator). I (Terrel Shumway) actually like this better: The code is not cluttered by stuff that can change easily (routing). My sense is that Blueprints may take care of this in Flask, but I am too new to say anything definite.
|
||||
|
||||
|
||||
Other Answers
|
||||
-------------
|
||||
* https://www.digitalocean.com/community/tutorials/how-to-structure-large-flask-applications
|
||||
* http://mattupstate.com/python/2013/06/26/how-i-structure-my-flask-applications.html
|
||||
* https://github.com/mattupstate/overholt
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue