On Jul 29, 10:36 am, Chris Angove <[email protected]> wrote: > That does indeed work. I am not in love with the idea of using > internal functions (_push_object), but as I see no other solution to > the problem I will go with it. Is this something that might be fixed > in a patch someday?
I think _push_object is named that way to avoid clashing with attributes you set, so I'm not sure it's supposed to be private in the usual sense. The next version of Pylons should have a fix for this that uses _push_object in the base test controller you get with `paster create`. I came up with something similar, which I pasted here: http://pylonshq.com/pasties/2ac38b74fa2e5d09467acdab3538f920 -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
