[Pywps-dev] clarification of dependencies

[Luís de Sousa]

Some quick answers (without looking much at the code):

> - is GDAL an absolute requirement?  For example, our soon to be published
>   instance of PyWPS does not use GDAL whatsoever
> - is OWSLib an absolute requirement?  For example, our soon to be published
>   instance of PyWPS does not use OWSLib whatsoever

OWSLib at least should be required to retrieve WFS/WCS complex inputs.
If it is not being used presently then something is likely wrong... I
believe OWSLib then requires GDAL for the job.

> - is werkzeug an absolute requirement?  For example, Can I swap in
>   Flask instead?

As far as I remember, Flask depends on Werkzeug (and Jinja). But it
might be a good idea to try something exclusively dependent on
Werkzeug.

> - unipath is used in one single spot in the entire codebase
> https://github.com/geopython/pywps/blob/aed9f6b4b76f954a9a401309ecebb5a22a99d495/pywps/wpsserver.py#L37
>   Any objections to working around this functionality thereby removing the
> unipath
>   dependency requirement?

None from my side, as long as the functionality stays there.

> My goal here is to have setup.py, tox.ini, and docs/conf.py derive from
> requirements.txt (for mocking for rtfd.org), but I'm not aware of the
> context/details behind the above.

I agree this would be a relevant improvement.

Luís