Were you prompted to update within GoogleAppEngineLauncher or did you
manually choose to update by selecting "Check for Updates" in
GoogleAppEngineLauncher's Help menu?

- Jason

On Sat, May 9, 2009 at 5:08 PM, Kwame <[email protected]> wrote:

>
> I just upgraded to version 1.2.2 and I'm getting a similar error:
>
> Exception exceptions.SystemError: 'error return without exception set'
> in <generator object at 0x3033300> ignored
> ERROR    2009-05-10 00:04:36,585 __init__.py:385] __init__() got an
> unexpected keyword argument 'keys_only'
> Traceback (most recent call last):
> ...
>
>   File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/
> GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/
> google/appengine/ext/db/__init__.py", line 1381, in get
>    results = self.fetch(1)
>  File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/
> GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/
> google/appengine/ext/db/__init__.py", line 1425, in fetch
>     raw = self._get_query().Get(limit, offset)
>   File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/
> GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/
> google/appengine/ext/db/__init__.py", line 1590, in _get_query
>     keys_only=self._keys_only)
> TypeError: __init__() got an unexpected keyword argument 'keys_only'
> ...
>
>
> I'm not using BookmarkQuery, so how do I fix this???
>
> Please help!
>
> On May 8, 11:04 am, Manu <[email protected]> wrote:
> > Hi!
> >
> > Thanks a bunch!
> > That fixed all :D:D:D
> >
> > Will that work after the upcoming release?
> > Can I ask you (if you have time, tell me, if not, no problem)
> > why was that failing? I'd really like to understand a little more.
> >
> > Also, I'd like to understand how all of this BookmarkQuery works...
> > I'll have to read the source and learn a bit
> > Thanks for your time!
> >
> > Manu
> >
> > On 8 mayo, 11:27, "Nick Johnson (Google)" <[email protected]>
> > wrote:
> >
> > > Hi Manu,
> >
> > > For now you can get things working again by replacing lines 36 and 37
> > > of bookmark.py with this:
> > > ---
> > >     def __init__(self, kind, filters={}, _app=None, keys_only=False):
> > >         super(BookmarkQuery, self).__init__(kind, filters, _app,
> keys_only)
> > > ---
> >
> > > -Nick Johnson
> >
> > > On Fri, May 8, 2009 at 3:15 PM, Manu <[email protected]> wrote:
> >
> > > > the code for BookmarkQuery is here:
> > > >http://bitbucket.org/moraes/appengine/src/422cc9b9473b/bookmark.py
> >
> > > > I'm using it but haven't developed it myself, so I don't really know
> > > > how it works.
> > > > Please help me, isn't there a way to quickly fix this at least for
> the
> > > > moment?
> > > > Thanks in advance!
> >
> > > > Manuel
> >
> > > > On 8 mayo, 02:05, ryan 
> > > > <[email protected]<ryanb%[email protected]>>
> wrote:
> > > >> hi manuel! we pushed a new version of our API code to production
> > > >> recently in preparation for an upcoming release, which has caused
> > > >> problems for people who use forked versions of some of our API code,
> > > >> like the problem described inhttp://
> groups.google.com/group/google-appengine/browse_thread/thread/...
> > > >> , or code that reaches below our API layer, which it sounds like
> > > >> BookmarkQuery does.
> >
> > > >> i don't have the BookmarkQuery source, so i don't know the exact fix
> > > >> you need, but the problem stems from a new optional keyword argument
> > > >> that we added to the Query classes' constructors. try adding a
> > > >> keys_only=None parameter to BookmarkQuery's constructor and see if
> > > >> that helps.
> >
> >
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" 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/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to