<div dir="auto"><div dir="auto">Thanks for everyone who participated!</div><div dir="auto"><br></div><div dir="auto">I declare this motion passed with the following votes from PSC members:</div><div dir="auto"><br></div>+1 from EvenR, HowardB<div dir="auto">+0 from KurtS, JukkaR</div><div dir="auto">-0 from SeanG</div><div dir="auto"><br></div><div dir="auto">Idan</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 26 Mar 2021, 18:57 , <<a href="mailto:Matt.Wilkie@yukon.ca" target="_blank" rel="noreferrer">Matt.Wilkie@yukon.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-CA" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">Thanks, that’s exactly the info I needed to get oriented.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1f497d">-Matt<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Idan Miara <<a href="mailto:idan@miara.com" rel="noreferrer noreferrer" target="_blank">idan@miara.com</a>>
<br>
<b>Sent:</b> March 26, 2021 5:29 AM<br>
<b>To:</b> Matt.Wilkie <<a href="mailto:Matt.Wilkie@yukon.ca" rel="noreferrer noreferrer" target="_blank">Matt.Wilkie@yukon.ca</a>><br>
<b>Cc:</b> gdal dev <<a href="mailto:gdal-dev@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">gdal-dev@lists.osgeo.org</a>><br>
<b>Subject:</b> Re: [gdal-dev] Motion: RFC 78: gdal-utils package<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Hi Matt,<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Point noted. I've updated the Summary section:<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Idan<u></u><u></u></span></p>
</div>
<div>
<h2 style="margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm;box-sizing:border-box">
<span style="font-family:"Segoe UI",sans-serif;color:#24292e">Summary<u></u><u></u></span></h2>
<p style="margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm;box-sizing:border-box">
<span style="font-family:"Segoe UI",sans-serif;color:#24292e">This RFC suggests to put all the GDAL python modules (formly scripts), except from the GDAL core SWIG bindings, into their own distribution on pypi. The GDAL python sub-package osgeo.utils (introduced
in GDAL 3.2) would be renamed into a package named osgeo_utils.<u></u><u></u></span></p>
<p style="margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm;box-sizing:border-box">
<span style="font-family:"Segoe UI",sans-serif;color:#24292e">The standalone python scripts from GDAL <= 3.1 were transformed to osgeo.utils in GDAL 3.2. For backwards compatibility these scripts still exist and function as tiny wrappers around the python modules.
Users of these scripts would not be effected from this RFC as the scripts would continue to function in GDAL 3.3 in the same way as in GDAL <= 3.2.<u></u><u></u></span></p>
<p style="margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm;box-sizing:border-box">
<span style="font-family:"Segoe UI",sans-serif;color:#24292e">To allow maximum backwards compatibility, The osgeo package (which includes the GDAL core SWIG bindings) and the osgeo_utils package will continue to be distributed in a single sdist named gdal in
pypi.<u></u><u></u></span></p>
<p style="margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm;box-sizing:border-box">
<span style="font-family:"Segoe UI",sans-serif;color:#24292e">In addition, a new pure python wheel distribution named gdal-utils will be available in pypi under the name gdal-utils.<u></u><u></u></span></p>
<p style="margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm;box-sizing:border-box">
<span style="font-family:"Segoe UI",sans-serif;color:#24292e">This will allow users who wish to upgrade the utils without upgrading the bindings to do so with pip install --upgrade gdal-utils (see more details in the following sections).<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">On Fri, 26 Mar 2021 at 00:11, mhw-at-yg <<a href="mailto:matt.wilkie@yukon.ca" rel="noreferrer noreferrer" target="_blank">matt.wilkie@yukon.ca</a>> wrote:<u></u><u></u></span></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Having been away from gdal-dev for some years, happily existing as an end of<br>
the line tool only user, and only recently re-engaging with the development<br>
community I have nothing to say on the strength and validity the RFC. <br>
<br>
I would like to comment though that it doesn't have a high altitude overview<br>
and say what gdal-utils is and where to look at it now. For instance is it<br>
all the files in ./gdal/swig/python/scripts/? or gdal/swig/python/osgeo/? or<br>
even gdal/swig/python? or somewhere else I haven't looked yet. It needn't be<br>
a lot words (there's so much there already it's hard for a newcomer like me<br>
to make out the structural bones). One sentence and a link would probably do<br>
it.<br>
<br>
I am excited about the prospect of a gdal-utils sub project, whether it<br>
remains within the core repository or is carved off into it's own. It would<br>
be a named place where my skills have a chance of contributing little<br>
somethings, and I could easily ignore the much larger set of things I don't<br>
understand in GDAL proper. ;-)<br>
<br>
cheers,<br>
<br>
<br>
<br>
-----<br>
-Matt<br>
--<br>
Sent from: <a href="http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html" rel="noreferrer noreferrer" target="_blank">
http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html</a><br>
_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><u></u><u></u></span></p>
</blockquote>
</div>
</div>
</div>
</blockquote></div>