Re: [google-appengine] Existing ndb data -> Python 3 data

2019-02-12 Thread 'Rahul Ravindran' via Google App Engine
That is the idea. I encourage you to participate in the early releases etc to ensure your use case is being met. You may have additional steps to enable caching. On Tue, Feb 12, 2019 at 5:30 PM Bruce Sherwood wrote: > That is very good news indeed. It's not immediately obvious from that >

Re: [google-appengine] Existing ndb data -> Python 3 data

2019-02-12 Thread Bruce Sherwood
That is very good news indeed. It's not immediately obvious from that site's Migration document whether the new ndb library is intended just to be something that will make it easy for someone familiar with the existing ndb library to build a new GAE, or rather that the intent is to make it

Re: [google-appengine] Existing ndb data -> Python 3 data

2019-02-12 Thread 'Rahul Ravindran' via Google App Engine
Development of the new Python 3-compatible ndb client is happening in the Google Cloud Python client library github repo at https://github.com/googleapis/google-cloud-python/tree/master/ndb . The library is not usable as-is yet, but work is in progress and can be monitored there. On Tue, Feb 12,

[google-appengine] Existing ndb data -> Python 3 data

2019-02-12 Thread Bruce Sherwood
I've seen the documentation on Python 3 datastores, but what I haven't seen is how to deal with preserving existing user data. My existing GAE (Python 2.7, standard environment, ndb) has 60,000 user records. Perhaps one way to preserve this data would be to add code to my current Python server