On Sat, Mar 3, 2012 at 15:39, Kaan Soral <[email protected]> wrote: > "NDB is an experimental, innovative, and rapidly changing new feature for > App Engine. Unfortunately, being on the bleeding edge means that we may make > backwards-incompatible changes to NDB. We will inform the community when > this feature is no longer experimental." > > How much of this warning will still be valid?
Good question. I wish I could guarantee that the 5 issues mentioned in my original email under "INCOMPATIBILITIES" are the last incompatible changes, but of course it's never done until it's done, and it's *possible* that we'll find some more things that we'd like to change before drawing the line in the sand. However you can tell from the list of incompatibilities that they are definitely edge cases. The changes in transaction semantics are the most serious IMO, but it's always possible that someone has accidentally put strings over 500 characters in a StringProperty (or over 500 bytes in an indexed BlobProperty). Still, no methods, functions or classes were renamed, and no signatures changed. I hope to continue this trend. In any case, I can't remind people enough that (at least) these incompatibilities will hit production when the 1.6.4 SDK goes out (actually production will see them a few days earlier) so please review your code, and if possible test with NDB 0.9.9. I also hope that 1.6.4 will see NDB's "experimental" label removed -- but no guarantees! -- --Guido van Rossum (python.org/~guido) -- 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.
