if its a pile of function calls, and you feel that walls between the database and code would be a pain, then probably flask. Its good for taking something and t

if its a pile of function calls, and you feel that walls between the database and code would be a pain, then probably flask. Its good for taking something and throwing a UI on it If you think "golly gosh, maybe some abstraction between the database and the code, hell, maybe even one of those wonderful Model View Controller things, whatever they are, would be great fun" then probably go for django or any other MVC framework Flask can do all that, but it requires your help to achieve it. You get control over what ties with what. Django is already set up for usage, just put your code in one of three boxes, and done, but you can't decide what those boxes are or how to use them. It brings a standard structure but you lose control.