[GeoNode-devel] The "gsconfig" module thing!

[Toni Schönbuchner]

Dear Community,

regarding below message of Alessio. The old library gsconfig has been replaced 
in master with following commit: https://github.com/GeoNode/geonode/commit/92ed66c7d6e20147414e9a28a3f63f43ba0b76fd <https://github.com/GeoNode/geonode/commit/92ed66c7d6e20147414e9a28a3f63f43ba0b76fd>
The commit will be soon backported to branch 2.10.x (latest release).

A word of caution: In case you’re using the old gsconfig with new code you might
run into problems: To reflect those changes don’t forget to run the well known

pip install -r requirements.txt — upgrade 

after your pull: 

Cheers,

– T.


> Am 10.07.2019 um 10:01 schrieb geonode-users-request at lists.osgeo.org:
> 
> Dear GeoNode devs, users,
> as you might already know, GeoNode relies on a python library, started by
> boundless several years ago, called "gsconfig", which basically handles
> almost all the APIs communication with GeoServer.
> 
> Currently, the library seems to be abandoned and messed up.
> There are tentatives to make it compliant with Python 3, but the code is
> full of errors and they do not accept PRs anymore.
> 
> With the latest versions of GeoServer, we need to update some API calls.
> Moreover, very soon, we will need to make this fundamental library
> compliant with Python 3.
> 
> Probably the easiest way would be to fork this library and create a
> "gsconfig3" or something hosted by the GeoNode github repo.
> 
> Any thoughts? Comments or feedbacks?
> 
> Alessio.
> 
> -- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20190717/14e5044f/attachment.html>