djangoforms ModelForm is the same as the regular Django form class (django.forms.Form) but with additions that allow it to interact with datastore models.
If you want to keep most of your form code and only have to update any of the GAE model specific stuff you do you can just include the latest Django library in your app.yaml and use the regular Django forms). I am in the process of doing this with one of our big apps. If you want to get rid of Django entirely in your Py27 version then WTForms is a good option but if you are happy with Django and don't want to re-write everything I recommend using the regular Django forms library. Best of luck. If you run into any gotchas along the way please share your solutions. And if you have particular questions I might know the answers as I am dealing with this now. - Bryce On Monday, April 15, 2013 2:14:06 PM UTC-7, Peter Chen wrote: > > Hi, I have a very large application hosted on google appengine which uses > many djangoforms. Since now djangoform is not supported by google appengine > anymore, I need to replace all of them, but I really don't want to, > because there are so many of them. Is there any way I can put the > djangoform back into my application? > > Peter > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
