Return render_template('error.html', message=e) Title='Import Results', import_d = import_d) Return render_template('/reviews/import_csv_results.html', Import_d = process_review_import(cform, rbform, csv_form) If cform.validate_on_submit() and rbform.validate() and csv_form.validate(): Rbform = administrative_form.ReviewBatchForm()Ĭform.customer_type.choices = Ĭform.bill_type_select.choices = For example, in reviews.py, I have something like: preload_reviews():īc, ct_list, bt_list = create_cus_billtype_lists(None)Ĭsv_form = administrative_form.ReviewCSVImport() Secondly, each of the views has the route as well as application logic, which I'm beginning to think that application logic should be separated elsewhere but I don't know where. Should the models file be split up into a package? It currently defines every table and database in a single file (it's over 5K lines) and most of my queries are defined there (but most logic on what to do with that data is elsewhere). Models is an example of a file that has grown rather unwieldy over time. I use the functional organization method, which I like but feel there's room for improvement: yourapp/ My Flask project is growing in size and I think it should be better organized than it is. I'm sure this question has been answered somewhere else but I keep searching every once in awhile and can't find a good answer.

Flask blueprint route methods post