[mapserver-dev] Python MapScript

[Lime, Steve D (MNIT)]

Agree'd... No RFC necessary - especially since your talking about at least some documentation updates. 

As for Swig versions, swig 3.0 is almost 4 years old and would be a reasonable target IMHO. I'm assuming that the PHP7 bindings also require a newer version. Finding someone to adopt the C# bindings might be a challenge. It would be nice if all bindings compiled under 3.x as part of the 7.2 release.

--Steve

-----Original Message-----
From: mapserver-dev [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Tom Kralidis
Sent: Monday, April 09, 2018 4:27 PM
To: Howard Butler <howard at hobu.co>
Cc: mapserver-dev at lists.osgeo.org Mailing List <mapserver-dev at lists.osgeo.org>
Subject: Re: [mapserver-dev] Python MapScript

+1 echo Howard. Happy to help where I can on this one.

..Tom

Sent from my iPhone

> On Apr 9, 2018, at 09:48, Howard Butler <howard at hobu.co> wrote:
> 
> +1 to all of it, and I don't think you need an RFC to do any of it.
> 
>> On Sat, Apr 7, 2018 at 1:29 PM, Seth G <sethg at geographika.co.uk> wrote:
>> Hi list,
>> 
>> I'd like to continue the push in cleaning up the Python MapScript bindings,  and getting a release to PyPi (for Python 2 and 3).
>> There are a number of things that can be removed as part of this, but I'd like to get opinions, points of view, and clarifications on a few things.
>> 
>> - as I understand it the GD rendered has been removed since v7.0 of MapServer. This means the "USE_GD" flag will always be 0, and therefore the pygdioctx additional code can be removed? https://github.com/mapserver/mapserver/blob/master/mapscript/python/pygdioctx/pygdioctx.h#L50
>> - cmake is now used to build the Python bindings so (please correct any incorrect assumptions) all the custom code in https://github.com/mapserver/mapserver/blob/master/mapscript/python/setup.py is now redundant, and a much simpler setup.py can be written to create wheels to upload to PyPI.
>> - Python3 bindings only seem to work correctly with newer versions of SWIG. Is there any minimum we need to support? The C# ones only seem to compile with 1.3.x - but fixing this doesn't seem insurmountable. Ideally we can say only v3+ is officially supported.
>> - The Python MapScript README is now 11 years old and refers to Python 2.2 - this can be extensively rewritten, and published as part of a PyPI release.
>> 
>> Does the above warrant a RFC?
>> 
>> Regards,
>> 
>> Seth
>> 
>> --
>> web:http://geographika.co.uk
>> twitter: @geographika
>> _______________________________________________
>> mapserver-dev mailing list
>> mapserver-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
_______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-dev