This has taken way too long and it's way out of topic. I won't bother answering inline anymore. If you want to think it's api change then fine go ahead this is no api at all as you don't even need quickstart to have a TG2 project. If you keep insisting it changes the API fine I won't argue about that.
In the meanwhile we have a broken tgext.pages (see the thread from GSOC for the first user figuring that out) But don't worry when people complain about how inflexible websetup is we'll point them to this thread. On Mon, Mar 23, 2009 at 2:21 PM, Gustavo Narea <[email protected]> wrote: > And apologies, I slipped in that part while trying to trim the email. > > My thoughts on your proposal: > 1.- It'd still be an API change, it just happens to be smaller: no new > modules, but two new functions. whatever, you are making a huge deal out of splitting a function into 3 logical functions which by the way everyone already does. > 2.- It'd still outdate some texts, like mine where I say something like "Add > the contents of Listing N right before DBSession.flush() and commit()". > which are probably way unflexible, and again it's totally fixable. 15 def setup_app(command, conf, vars): 16 """Place any commands to setup {{package}} here""" 17 load_environment(conf.global_conf, conf.local_conf) 18 setup_schema(command, conf, vars) 19 bootstrap(command, conf, vars) 20 DBSession.flush() 21 transaction.commit() --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
