On Fri, Dec 25, 2009 at 8:42 PM, Aurelio Tinio <[email protected]> wrote: > On Fri, Dec 25, 2009 at 11:14 AM, Waldemar Kornewald <[email protected]> > wrote: >> >> We've switched to a new Django port which supports Django models. It's >> not ready for most people, though, and we need more help. >> > > How can we help? Is there another repository where the new Django port can > be accessed?
You should contribute to the port here: http://bitbucket.org/wkornewald/django-nonrel-multidb/ Also, this thread could be helpful: http://groups.google.com/group/django-developers/browse_thread/thread/fcf501d073ae33f/991c97811ea1412f Just tell me your bitbucket username when you need commit access. We plan to blog about the port in the next weeks, so the first fearless users can play with it, but we don't even support list properties, so don't expect that you can build anything big with it. Also, we'd prefer to clean up the current port before adding new features. For those who can't help with the port, an alternative project would be to make Django more lazy-loading. For this you just need to find out which modules get loaded unnecessarily and move the imports into functions, for example. The dev_appserver has a --debug_imports parameter which can be helpful, here. You could also create a minimalistic Django view (no template rendering!) and print out ordered(sys.modules.keys()). Another idea would be to modify dev_appserver's source to print out module imports as a tree, so you know which module is responsible for which import. Happy New Year! Waldemar Kornewald -- 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.
