Created attachment 210804 [details] pygeoapi 0.6.0 graphics/pygeoapi: OGC API server implementation pygeoapi is a Python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy an RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license. QA: * portlint: OK (looks fine.) * testport: OK (poudriere:11/12/13, i386/amd64) * maketest: OK (manual tests only, see https://github.com/geopython/pygeoapi/issues/339)
^Triage: Reporter is committer, assign accordingly
Review: - Upstream has 0.7.0 out - Package provides console_scripts, port must be concurrent safe (USE_PYTHON=concurrent) - Package provides tests in sdist, add TEST_DEPENDS and test target [1] - pytz and python-dateutil are declared upstream as a dependencies (requirements.txt parsed into setup.py), but are not listed in *_DEPENDS [1] cd ${WRKSRC} && ${PYTHON_CMD} -m pytest -v -rs -o addopts=
Created attachment 210834 [details] pygeoapi 0.7.0 Changes: - Update to 0.7.0 - add USE_PYTHON=concurrent - add two new dependencies for 0.7.0: pytz and python-dateutil koobs@ sorry, but PyPi tarball doesnt ship tests subdir and if we want test it we need a pgsql, elasticsearch, mongodb bases graphics/gdal built with SQLite, etc. I think it's best if I work on an upstream CI, isnt' it?
other change: pygeoapi -> py-pygeoapi https://wiki.freebsd.org/Python/PortsPolicy#Naming
(In reply to Loïc Bartoletti from comment #3) Tests aren't compulsory (dont block commit), but they are highly valueable. At least it would be nice to ask upstream to ship the tests in the PyPI sdist (using MANIFEST.in is the usual way) Thanks for the updates, and note: you don't need to maintainer approval your own ports (but its great to be explicit, particularly if/when someone else is committing your updates) :)
Thanks koobs@ Should be fixed for the next release. I'll plan also to create a CI for this port.