I assume that you are seeing an error during the parsing of your appcfg.py file?
The error message should say that you can't use a CGI with threadsafe.
The solution is to use WSGI in your handlers instead i.e.
google.appengine.ext.mapreduce.application
google.appengine.ext.ereporter/report_generator.application
Cheers,
Brian
> Thanks,
>
> - Pol
>
> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
>
On Sat, Nov 12, 2011 at 7:46 AM, Pol <p...@everpix.net> wrote:
> Indeed the problem is the parsing of app.yaml:
> - url: /mapreduce(/.*)? script: $PYTHON_LIB/google/appengine/ext/
> mapreduce/main.py login: admin- url: /ereporter.* script:
> $PYTHON_LIB/google/appengine/ext/ereporter/report_generator.py login:
> admin
> So what do I use instead for script paths?
script: google.appengine.ext.mapreduce.application
script: google.appengine.ext.ereporter.report_generator.main.APP
> Looking into the SDK
> source, these extensions are not 2.7 multithreaded ready.
How so?
Cheers,
Brian
On Sun, Nov 13, 2011 at 8:05 AM, working <cor...@gmail.com> wrote:
> Hi Brian,
>
> As for
> google.appengine.ext.mapreduce.application
>
> Does it mean the SDK/runtime already has its mapreduce? Right now, I
> still supply an additional copy in my app folder. If SDK/runtime
> already has it, I will delete my own copy.
>
> How about the pipeline?
The SDK and runtime does include a copy of mapreduce but it is
recommended that you include your own copy because mapreduce is
experimental and incompatible changes may still be made. Including
your own copy will protect your from this.
Cheers,
Brian
Oops, I meant:
script: google.appengine.ext.mapreduce.main.APP
script: google.appengine.ext.ereporter.report_generator.application
Cheers,
Brian