And that error does not show up for me in my dev sandbox, not sure why. On Sun, Oct 23, 2011 at 2:33 PM, Dan Frankowski <[email protected]> wrote:
> See also > http://stackoverflow.com/questions/7799764/google-app-engine-python-2-7-runtime-importerror-cannot-import-name-djangofor > > When I try to run my AEP on python 2.7 in production, I get: > > ../common/appenginepatch/appenginepatcher/patch.py", line 574, in > fix_app_engine_bugs > from google.appengine.ext.db import djangoforms > ImportError: cannot import name djangoforms > > > So, uh, look out, people. > > > On Fri, Oct 21, 2011 at 10:18 AM, John Gardner <[email protected]> wrote: > >> It looks like there will be some changes to AEP required to support >> Python 2.7. >> >> See here: >> >> http://www.allbuttonspressed.com/using-dev_appserver-with-python-2-7-on-app-engine >> >> These changes have already been made to Django-nonrel. Since there >> are a number of us still using AEP, and there are still missing pieces >> that will block moving to Django-nonrel, I think it makes sense to >> update app-engine-patch to support 2.7. Otherwise, we'll all be >> updating our local copies independently, and that's closed source >> thinking. >> >> I see several committers besides Waldemar; any committers still >> monitoring this list? Otherwise, I see a fork coming. >> >> -John >> >> On Oct 19, 7:49 pm, johnP <[email protected]> wrote: >> > 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. >> >> > -- 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.
