MacPingu

> 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? yes....

I think we don't want to merge it but keep it as reference for the implementation of the `processes_path` (https://github.com/geopython/pywps/issues/118).

@tiranno @justb4 @tomkralidis Sounds like using `requests Session` could be an approach we could try. Maybe open a new issue for this? First I would like to get the current...

PR #611 is just a fix for wps module.

@tomkralidis should we make `lxml` a requirement ... and skip the special handling when `lxml` is not available?

I have "read the docs": * Not to much help: https://docs.readthedocs.io/en/latest/faq.html#my-project-isn-t-building-with-autodoc * RTD supports conda (beta), not tried yet: https://docs.readthedocs.io/en/latest/conda.html

There is a processing interface which already introduces a `cancel` method: https://github.com/geopython/pywps/blob/91da95ef846e4d9bce7cfd8016af467d2acfd1cb/pywps/processing/basic.py#L21 We are having several implementations of the processing interface: * multiprocessing (default but no `cancel` ) * scheduler...

@jachym @ldesousa can we use the mulitprocessing `terminate` or `kill` method to implement the WPS 2.0.0 *cancel* feature? https://docs.python.org/3.7/library/multiprocessing.html#multiprocessing.Process.terminate

We already introduced a service to handle the job queue in #505. I currently working on removing stalled jobs from the queue. Stalled jobs are identified by a timeout parameter...

> At the moment, process request is stored only in the table `pywps_requests` - once the process is started, it is deleted from this table and there is now way,...