[ckan-dev] ckanext-spatial and pycsw versions

Wed Apr 9 11:26:36 UTC 2014

Hi Tom,

The docs were written at the time that pycsw 1.8.0 wasn't still
around, hence the wording. I'm happy to move the requirement up to
pycsw 1.8.0, as ckanext-spatial already requires OWSlib 0.8.6 which
sometimes causes compatibility problems.

As for pycsw not being part of the pip-requirements.txt file I think
is fine, as I wouldn't expect most ckanext-spatial users to use it,
and may save some library compatibility problems to them, but have no
strong opinions on it.

Adrià

On 22 March 2014 10:32, Tom Kralidis <tomkralidis at gmail.com> wrote:
> Hi all: the docs at
> http://docs.ckan.org/projects/ckanext-spatial/en/latest/csw.html
> mention 1.6.1 as the minimum requirement.  Having said this, the docs
> also say:
>
> """If you get errors similar to this one, this is caused by
> limitations on the pycsw model definition. This should be fixed in
> future versions of pycsw:
>
> ERROR: not inserted f8d48eaf-780b-40b8-a502-7a903fde5b1c Error:ERROR:
> value too long for type character varying(256)"""
>
> This has been fixed in pycsw 1.8.0 [1] and a user mentioned that we
> should update the docs to reflect this, as they ran into this exact
> issue using pycsw 1.6.1, and upgrading pycsw to 1.8.0 fixed things.
>
> Should we update the docs to say the minimum requirement is 1.8.0? Or
> keep 1.6.1 and explicitly say this has been fixed in 1.8.0?  I would
> vote for moving to 1.8.0 as the minimum requirement, but am open to
> other options.
>
> FYI pycsw is not part of the pip-requirements.txt install, yet is
> installed manually via git.
>
> I'll prepare a PR based on the results of this discussion.
>
> Thanks
>
> ..Tom
>
> [1] https://github.com/geopython/pycsw/issues/179
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev