-
Put PYWPS_PROCESSES and PYWPS_CFG env variables back to PyWPS (demo)
Related ticket:
https://github.com/geopython/pywps/issues/118
-
reimplement process discovery as it was in pywps-3
-
## Description
It happens quite often that we have a set of processes with common input (and output) parameters. In WPS the process signature (inputs+outputs) is called a *profile* (I think). To av…
-
# Description
We are using a cookiecutter to setup new pywps projects:
https://github.com/bird-house/cookiecutter-birdhouse
Should we use the cookiecutter to maintain this pywps demo?
Should…
-
There seems to be an incompatibility between the latest versions of `pywps` (4.5.0) and `pywps-flask` (master branch as of today).
```shell
$ git clone https://github.com/geopython/pywps-flask.git…
-
For Geoserver WPS: http://docs.geoserver.org/2.7.0/user/community/scripting/py/index.html
For PyWPS-4: https://github.com/jachym/pywps-4
-
## Description
The PyWPS demo is an app build with [Flask](http://flask.pocoo.org/):
https://github.com/geopython/pywps-flask
It is not necessary to use it, it would add another dependency ... …
-
## Description
CLI is used for development and debugging. It would be nice if it cleans up the logs when starting the pywps service (maybe optionally).
-
We could write a `pytest` extension to support testing of `PyWPS` services but also for testing WPS clients, like `birdy`.
This extension could be a python package on its own ... but we might also …
-
Python 3.x (starting with 3.5) is more and more used. climaf is currently only supporting Python 2.7. It would be nice if climaf can support both 2.7 and 3.x (>=3.6).
Compatibility can be achieved …