Jachym Cepicky

Hi all, did some contribution to PyWPS in the past. I confirm that my contributions to PyWPS is compatible with the PyWPS license guidelines at the time of contribution. Sebastian...

Hi, this is confusing, as @cehbrecht says: ProcessFaild strucutre is part of status report - which returns 200 code. But generally speaking, I would support more "aggressive" error handling and...

maybe we should call for PSC meeting and discuss all the things for 4.2

Hi I was helping to Adam with this (making it to single commit). But this single commit does not seem to work properly according to Adam's tests. Now he is...

Hi, OWC seems something we need to support and seems to bring the (at least to me) important topic "containerization" of running jobs. @allixender I think, if you are interested...

Just noting, that this is slightly out of my scope, so if you feel I should contribute somewhere or do something, which would help with PyWPS development, please write me...

Hi it's on my to-do list, but I would suggest, we move it to 4.4

Are we talking about those files? ``` grep -r "etree.tostring" pywps/*/*.py pywps/app/WPSRequest.py: return lxml.etree.tostring(value_el, encoding=unicode) # noqa pywps/app/WPSRequest.py: return lxml.etree.tostring(value_el, encoding=str) pywps/inout/inputs.py: data["data"] = etree.tostring(data_doc, pretty_print=True).decode("utf-8") pywps/inout/inputs.py: data["data"] = etree.tostring(etree.CDATA(self.base64))...

this is an oldone - don't we have already code for automatic process import in the `master` branch ? `processes` configuration option, which is pointing to Python module?

#56 is kind of pre-step to some of 2.0.0 features, yes, it's related út 16. 2. 2016 v 0:59 odesílatel Tom Kralidis [email protected] napsal: > @jachym https://github.com/jachym is this related...