Is there a reason that a pyramid_sqla template does not add 'pyramid_sqla' as a dependency of the generated project, considering that the project is doing imports from the pyramid_sqla package?
Michael On Thu, Jan 27, 2011 at 2:36 PM, Daniel Holth <[email protected]> wrote: > stucco_auth's "the approach" includes: > > 1. SQLAlchemy session is only available as request.db (as far as > stucco_auth is concerned). > 2. Transaction management. No .commit() or .rollback() in view code. > 3. Each package has its own declarative_base() and its own versioned schema > > It has no paster template. It would work fine if request.db = > pyramid_sqla.get_session(). > > I am more interested in the reusability story than the quick start story. > Something like: > > 'pip install pyramid_wiki' > root = dict(wiki=pyramid_wiki.Wiki()) > create_tables(session, 'pyramid_wiki') > config.include(pyramid_wiki.config) > > http://localhost:6543/wiki/ > > > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<pylons-discuss%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
