[Pywps-dev] clarification of dependencies
Jachym Cepicky
jachym.cepicky at gmail.com
Tue Feb 16 18:49:07 PST 2016
hi
>>
> >> - is GDAL an absolute requirement? For example, our soon to be
> published
> >> instance of PyWPS does not use GDAL whatsoever
> >
> >
> > nope, it's there just for input data validation. but just for some cases
> > (STRICT validation) and it's used by tests
> >
>
> I wonder if we can make this an OPTIONAL requirement/dependency
> and isolate the GDAL/OGR based code to a point where we could
> try/except the package/module import. Then if that codepath is hit
> PyWPS will throw an ows:ExceptionReport.
>
> Of course GDAL would be part of our Travis-CI setup.
>
> https://github.com/geopython/pywps/issues/86
> >>
> >> - is OWSLib an absolute requirement? For example, our soon to be
> >> published
> >> instance of PyWPS does not use OWSLib whatsoever
> >
> >
> > yes - we rely on it
> >
>
> OK
>
rewriting in a way similar to pycsw is option
>
> >>
> >> - is werkzeug an absolute requirement? For example, Can I swap in
> >> Flask instead?
> >
> >
> > Quoting from http://werkzeug.pocoo.org/
> >
> > Werkzeug is the base of frameworks such as Flask and more
> >
> > IMHO Flask should be able to install it's dependences automatically (?)
> >
>
> So here werkzeug is being for more than just a WSGI front end?
>
weeell, this was originally setuped by Alex, who started this. I have
actually no deep clue about how it works all together (no need yet). Needed
more investigation
J
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20160217/451763ed/attachment.html>
More information about the pywps-dev
mailing list