Hi Ben,

It's difficult to know what this stack trace means with out an idea of what
kind of obj the has_key method belongs to.  Would it be possible to at least
provide the template that is being rendered? And a description of what one
expects to be rendered?

-Marzia

On Fri, Nov 14, 2008 at 11:51 AM, Ben Adida <[EMAIL PROTECTED]> wrote:

>
> Marzia,
>
> It's a little difficult to cut down the example to size, because *all*
> of my pages that render content from the store are giving errors.
> Here's one URL where the issue comes up:
>
>
> http://dev.heliosvoting.org/elections/ahBkZXYtaGVsaW9zdm90aW5ncg8LEghFbGVjdGlvbhiRAww/view
>
> and that will give you the complete stack trace.
>
> Let me know if that helps, and thanks.
>
> -Ben
>
> On Nov 14, 9:49 am, Marzia Niccolai <[EMAIL PROTECTED]> wrote:
> > Hi Ben,
> >
> > Can you provide a more complete example of the code that causes this
> issue?
> > As well as the complete stack trace.
> >
> > Thanks,
> > Marzia
> >
> > On Fri, Nov 14, 2008 at 9:40 AM, Ben Adida <[EMAIL PROTECTED]> wrote:
> >
> > > Suddenly, I'm getting the following errors on just about every page:
> >
> > > if hasattr(obj, 'has_key') and obj.has_key(key):
> > > TypeError: has_key() takes exactly 1 argument (2 given)
> >
> > > This is within the Cheetah templating library, _valueForName function.
> > > I haven't modified the Cheetah code, nor have I modified my
> > > application at GAE in the last few days.
> >
> > > And I can't reproduce this error in my local SDK installation.
> >
> > > Did GAE just change some internal libraries? I don't even understand
> > > why has_key() would ever take only one argument...
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to