Marzia,

I don't want to seem disagreeable, unappreciative, or anything like
that.  But I really have to agree with Ben on this one.

It seems to me that this change introduces a bug.  I've been using
python for 8 years now, and I can't think of any reason for a has_key
method to take only one argument (its parameter list is always (self,
key_name)).  That's a fairly core part of the language.  If you're
going to introduce a new method that does something vaguely similar,
but changes things significantly like this, IMHO, you should really
give it a different name.

Then again, you do have Guido on hand, and his whim certainly trumps
anything anyone else might say.  Maybe he's already vetted this
decision, and I need to just shut up and mind my own business.

Thank you for the help and support you're providing,
James

On Nov 17, 6:10 pm, Marzia Niccolai <[EMAIL PROTECTED]> wrote:
> Hi Ben,
>
> It's certainly not our desire to introduce any changes in the App Engine
> library that would break our users app, but from time to time some parts of
> the apis and libraries will be modified to fix issues/enhance features.
>
> When these fixes happen, it's always possible that this will break a certain
> subset of applications who are implicitly or incorrectly assuming certain
> features of the API.  Of course, we'd like to avoid this when possible, but
> sometimes it's difficult to anticipate how some of these changes can affect
> certain applications.
>
> We are certainly working on finding the right balance, and hope that as we
> continue development with App Engine these kind of things will happen less
> often.
>
> -Marzia
>
--~--~---------~--~----~------------~-------~--~----~
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