Re: Pyramid status update...

Chris, I can possibly provide pyramid-jinja2 i18n docs, but I am not sure if I've taken a decent approach. I started following the project a few weeks ago. I like it. While reading through the docs, I was playing along by modifying shootout (https://github.com/jeffmad/shootout). I changed it to

Re: Pyramid status update...

Am 12.01.2011 12:02, schrieb Chris McDonough: > The intent is to have only one non-conditional paster template in the > core distribution, but this work might be useful to other paster > template developers. Ok, maybe these templates could go into a supplementary package then. TurboGears 2 has the

Re: Pyramid status update...

On Wed, 2011-01-12 at 11:56 +0100, Christoph Zwerschke wrote: > Am 12.01.2011 11:30, schrieb Chris McDonough: > > I'm not a big fan of conditionalized templates, as they're even harder > > to test than non-conditionalized ones (we don't even yet have automated > > tests for the non-conditionalized

Re: Pyramid status update...

Am 12.01.2011 11:30, schrieb Chris McDonough: > I'm not a big fan of conditionalized templates, as they're even harder > to test than non-conditionalized ones (we don't even yet have automated > tests for the non-conditionalized ones). As these would be integration or system tests anyway, I don't

Re: Pyramid status update...

On Wed, 2011-01-12 at 11:26 +0100, Christoph Zwerschke wrote: > Am 12.01.2011 10:03, schrieb Chris McDonough: > > - Figure out how to slim the herd of paster templates. > > You can use http://pythonpaste.org/tempita/ to make case distinctions in > the paster templates, so you don't need to create

Re: Pyramid status update...

Am 12.01.2011 10:03, schrieb Chris McDonough: > - Figure out how to slim the herd of paster templates. You can use http://pythonpaste.org/tempita/ to make case distinctions in the paster templates, so you don't need to create separate templates for every subfeature or option that involves only min

Re: Pyramid status update...

As the end of that message says, we'd like to have a beta out by the end of January. But that's a goal, not really a promise. - C On Wed, 2011-01-12 at 15:15 +0530, Raviteja wrote: > Hi Chris, > > We are a team, who started working on a web-application using pyramid. > Pyramid is very-well docu

Re: Pyramid status update...

Hi Chris, We are a team, who started working on a web-application using pyramid. Pyramid is very-well documented, and so we decided to develop using it, even if it's in alpha. We are very excited by the releases of the pyramid framework, and we wanted to be up-to-date so that we don't miss any dev

Pyramid status update...

Hi folks, Since the last status update I gave maybe a month or so ago, where I enumerated the list of "must-haves" for a 1.0beta Pyramid release (see ), we've had two more alpha releases (1.0a8 and