On Wed, 2010-11-24 at 00:30 -0500, Chris McDonough wrote: > On Tue, 2010-11-23 at 21:24 -0800, Mike Orr wrote: > > By the way, with the extensive reorganization of application templates > > proposed including restructuring the SQLAlchemy support, it puts me > > and Eric pretty much on hold for writing tutorials and demos, which I > > was planning to work on over the next five days. (Because I'm snowed > > in in Seattle plus the Thanksgiving holiday.) > > > > So it would be nice if we could decide the API quickly and get a draft > > implementation of 'pyramid' and 'pyramid_sqla' out, and then worry > > about getting the manual and tests caught up. That way we can do our > > work while the latter is being done. > > Maybe you could write pyramid_sqla? I have no desire to keep imposing > my own will on this set of choices, but whatever gets created needs a > champion and maintainer. > > There's no "API" that I know of, unless you mean something in the > pyramid_sqla package itself. But you can invent it rather than waiting > for it to be invented. And AFAICT, you don't need to care about the > "pyramid" template to make progress on a tutorial or demo. > > BTW, I see no chance of coming up with a frozen-in-time paster template > spec that is static and unchanging. I've been changing docs based on > required changes to paster templates for years.
(I should also note: it's a tremendous advantage to be both the docs author and the template maintainer, because you can quickly judge whether a template change requires docs changes and vice versa, and make those changes quickly without much spin-up time or overhead). - C -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
