Re: Terminology Change - Template to Skeleton

2011-03-20 Thread Mike Orr
On Sun, Mar 20, 2011 at 8:12 PM, Joe Dallago wrote: > This issue has been previously discussed, I just wanted to make sure > that everyone agrees.  At the moment the docs refer to "paster > templates" and renderered templates(mako, chameleon, jinja) using the > same name.  I propose that we change

Re: WebHelpers conflict #63 and #59

2011-03-20 Thread Mike Orr
On Sun, Mar 20, 2011 at 6:38 AM, Wichert Akkerman wrote: >>> New issue 63: Regression: paginate loads whole table when given >>> SqlAlchemy object >>> > Yaiks - that change will effectively kill any site which does pagination > over a large SQL table, so reverting it would be a good start. I don'

Re: Terminology Change - Template to Skeleton

2011-03-20 Thread Chris McDonough
Fine by me. - C On Sun, 2011-03-20 at 22:12 -0500, Joe Dallago wrote: > This issue has been previously discussed, I just wanted to make sure > that everyone agrees. At the moment the docs refer to "paster > templates" and renderered templates(mako, chameleon, jinja) using the > same name. I pro

Terminology Change - Template to Skeleton

2011-03-20 Thread Joe Dallago
This issue has been previously discussed, I just wanted to make sure that everyone agrees. At the moment the docs refer to "paster templates" and renderered templates(mako, chameleon, jinja) using the same name. I propose that we change the official nomenclature used to describe "paster templates

Re: New project . Pylons or Pyramid

2011-03-20 Thread Iain Duncan
On Sun, Mar 13, 2011 at 12:32 AM, Eric Ongerth wrote: > +1. If I chose Pylons over Django and TurboGears (not to mention > Rails) for its flexibility, light weight, and pluggability, Pyramid > offers more of those qualities than Pylons and with better docs, plus > built-in authorization/authentic

Re: WebHelpers conflict #63 and #59

2011-03-20 Thread Wichert Akkerman
On 3/20/11 09:04 , Mike Orr wrote: I got this bug report in WebHelpers 1.3b1: On Sat, Mar 19, 2011 at 9:36 PM, Bitbucket wrote: New issue 63: Regression: paginate loads whole table when given SqlAlchemy object https://bitbucket.org/bbangert/webhelpers/issue/63/regression-paginate-loads-whole-

Re: WebHelpers conflict #63 and #59

2011-03-20 Thread danjac...@gmail.com
Check if items is a sqlalchemy query would be an immediate fix. This can seriously kill a web server so paginate should be considered unusable with sqlalchemy until this is resolved. On 20 Mar 2011 08:04, "Mike Orr" wrote: I got this bug report in WebHelpers 1.3b1: On Sat, Mar 19, 2011 at 9:36

WebHelpers conflict #63 and #59

2011-03-20 Thread Mike Orr
I got this bug report in WebHelpers 1.3b1: On Sat, Mar 19, 2011 at 9:36 PM, Bitbucket wrote: > New issue 63: Regression: paginate loads whole table when given SqlAlchemy > object > https://bitbucket.org/bbangert/webhelpers/issue/63/regression-paginate-loads-whole-table-when > > nh2 on Sun, 20 Ma