On Feb 24, 2011, at 9:43 AM, Gael Pasgrimaud wrote: > On Thu, Feb 24, 2011 at 6:37 PM, Mike Orr <sluggos...@gmail.com> wrote: >> Paginate works with Pyramid, with the caveat that if you use the >> Page.pager() method, you have to pass a custom URL generator to the >> constructor as described on the webhelpers.paginate page. >> > > Can't we have a default pyramid generator (and well, webob based > frameworks) in WebHelpers who use the request.path to generate the url > ? > > So you can use Page.pager(request=request)
Yep, that was the thought for the next iteration. Also, to require the object being paginated to support the Python sequence API, so that the hacky code that tries to deal with various SQLA things isn't needed. Ie, there'd be some sequence wrappers for SQLA query objects vs. a bunch of if/else code toggling it inside the paginator. Cheers, Ben -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@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.
