On Jan 29, 2007, at 8:36 PM, dsmath wrote:
I've been evaluating pylons and so far I really like the framework ...
well, ummm, except for one problem. I've noticed that when running my
a web app I'm building, relations that are defined in ORM mapper are
not working very well at all. In
Hello,
I've submitted a ticket #184
(http://pylonshq.com/project/pylonshq/ticket/184) but it only has line
codes that Pylons devs will need to copy/paste into the code or so.
To make their life easier, I'd like to provide a real patch for the
devs. I'm not used to work with trac/svn, so I'd
I generally just
create a new session for the SA context in my BaseController as
mentioned in the QuickWiki docs.
Doh! I should have read the QuickWiki doc rather than skimming
it ;) For the impatient facing the same problem, here's a reiteration
of the methodology suggested in the
On Jan 30, 2007, at 4:16 AM, Alexandre CONRAD wrote:
I've submitted a ticket #184
(http://pylonshq.com/project/pylonshq/ticket/184) but it only has line
codes that Pylons devs will need to copy/paste into the code or so.
To make their life easier, I'd like to provide a real patch for the
On Jan 29, 1:07 am, Max Ischenko [EMAIL PROTECTED] wrote:
I run into an interesting issue with paste.fixture and url_for.
I have a simple test case:
class TestQuotesController(TestController):
def test_create(self):
eq_('/quotes/new;create', url_for(controller='quotes',
On Jan 30, 7:11 am, Christoph Haas [EMAIL PROTECTED] wrote:
The webhelpers.pagination.paginate call fails miserably if an object
is given as the first parameter that is a proper SQLObject class or
SQLAlchemy query. The error message was You shouldn't have this
which doesn't tell the user what
