Porting to Nonrel is great. But for my production app, the main need for Django has been the sessions/authentication framework and forms. Maybe a few utility functions here and there. Possibly i18n in the future. So AEP has been just fine for my needs. Maybe in the future, there will be a compelling reason to migrate (needing to host off of appengine, for example). I'll cross that bridge in the future, if necessary.
But now, there is a compelling reason to migrate to Python 2.7 - especially with AEP's new billing model. I have not started the migration, and will probably do so in December. In the meantime, I encourage folks to start sharing experiences about the process for all of our mutual benefit. I don't know if Waldemar still monitors this board. Do you have any thoughts about potential python 2.7 pitfalls? I do understand the 'migrate to nonrel' message. But AEP is also a worthy project - even if it's not bleeding edge at the moment :) johnP On Oct 19, 8:32 am, dan <[email protected]> wrote: > I started to try django-nonrel. > > My datastore has parent/child relationships, and that is not currently > supported in django-nonrel. > > Seehttps://groups.google.com/d/topic/django-non-relational/TkfERTYGtcQ/d... -- You received this message because you are subscribed to the Google Groups "app-engine-patch" 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/app-engine-patch?hl=en.
