you don't have to link it via app.yaml, you can map urlmap via django , just make sure that it points to the right page.
On Jun 12, 8:31 am, Luís Marques <[email protected]> wrote: > Hello, > > OK, it seems that the problem that is making this difficult is the > following. > > If the mapreduce tries to import module "myapp.foo.A", and module A > tries and fails to import module "myapp.foo.B", mapreduce reports that > A could not be found in path "myapp", instead of the import error that > occurs in A during its import. > > In my specific case, the error was importing Django, even though this > was not exactly obvious, given the misleading error. So, I suggesting > fixing this usability error. Perhaps I should open a bug report? > > Another question though is the following. In my main.py I have a > standard django initialization... > > from appengine_django import InstallAppengineHelperForDjango > InstallAppengineHelperForDjango() > (etc) > > ...followed by a main() execution which uses Django. When mapreduce is > finally included in GAE, I will not have control to modify the > mapreduce/main.py. So, how should I do to (efficiently) import/install > Django for use with mapreduce? > > I suppose an efficient technique will not repear the "install" inside > of the main(), but only do so once for each new instance? How do I do > this? I got problems creating a new main and calling mapreduce from > there, while trying to avoid patching mapreduce/main.py. > > Thanks, > Luís -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
