[EMAIL PROTECTED] wrote: > Still a bit worried about model.py getting unwieldy though... ;-) >
I think in most uses it will not be an issue. The potential headaches caused by namespaces and SQLObject are more of a worry to me. I think the best way to configure it is to use a single file by default but have an example of correct usage set up (and commented out) if you want to use multiple files. I agree that this is more important for controllers than models. That said I think having folders for templates, static content, and controllers, but not models will be confusing. I would say that the best way to set it up is to keep the current configuration but set up the necessary folders/files if people want to split up their code. Those that don't want it can remove the extra folders and delete the (commented out) imports. Those that do will have a much easier time getting that going. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
