<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">@Suzana<div class="">There is a ticket on PyWPS concerning celery:</div><div class=""><a href="https://github.com/geopython/pywps/issues/237" class="">https://github.com/geopython/pywps/issues/237</a></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 14 Dec 2018, at 8:37 pm, Carsten Ehbrecht <<a href="mailto:ehbrecht@dkrz.de" class="">ehbrecht@dkrz.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Suzana,<br class=""><br class="">unfortunately the developer of this Celery demo has left the project. I haven’t checked the demo/code … I just have seen it is using a PyWPS fork:<br class=""><a href="https://github.com/fderue/pywps.git" class="">https://github.com/fderue/pywps.git</a><br class=""><br class="">I know that this Celery demo is based on the scheduler extension which is part of pywps:<br class="">https://pywps.readthedocs.io/en/master/extensions.html#job-scheduler-extension<br class=""><br class="">This extension is by myself … and I don’t promise that it still works with python 3.x. Our test-suite does not cover enough and I will need to check this by myself again.<br class=""><br class="">Cheers,<br class="">Carsten<br class=""><br class=""><blockquote type="cite" class="">On 12 Dec 2018, at 12:36, Suzana Barreto <suzana.barreto@envsys.co.uk> wrote:<br class=""><br class="">Hi Everyone,<br class=""><br class="">Seasons greatings ;-). I am currently trying to find out if it is possible to use python Celery with PyWPS. I have had a look at the following docker demo project https://github.com/fderue/pywps_celery_demo. This works but is unfortunately running under python 2.7. My PyWPS server instance is running under 3.6, having run the celery example under 3.6, the server fails because it cannot serialize the job. The errors I get are "TypeError: write() argument must be str, not bytes" from the job.dump function, and if I change the function so that it opens the file in binary mode, then I get "io.UnsupportedOperation: underlying stream is not seekable" . <br class="">Does anyone know why this code is not 3.6 compatible? Does anyone know how I might be able to fix this?<br class=""><br class="">I have also tried to serialise the wps_response and wps_request objects separately but these are not serializable although the Process is. Any help would be greatly appreciated.<br class=""><br class="">Thanks in advance,<br class="">Suzana<br class="">-- <br class="">Dr Suzana Barreto<br class="">Software Analyst<br class="">Environment Systems<br class="">Tel: +44 (0) 1970 626688<br class="">www.envsys.co.uk<br class=""><br class="">The information contained in this e-mail is intended only for the use of the person(s) to whom it is addressed and may contain confidential or privileged information. If you have received this e-mail in error please contact the sender and delete the material without copying, distributing or disclosing the content. All reasonable precautions have been taken to ensure that this e-mail is free from any virus, however, the recipient should verify this to be the case. Please 'think before you print'<br class=""><br class="">_______________________________________________<br class="">pywps-dev mailing list<br class="">pywps-dev@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/pywps-dev<br class=""></blockquote><br class="">_______________________________________________<br class="">pywps-dev mailing list<br class="">pywps-dev@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/pywps-dev</div></div></blockquote></div><br class=""></div></body></html>