[gdal-dev] Motion: RFC 78: gdal-utils package

Fri Mar 26 04:56:58 PDT 2021

Hi Daniel,

I see what you mean, And I agree that gdal-utils should not be a dependency
or an extra-dependency for gdal.

This issue would be relevant anyway only if we decide to remove the utils
from the gdal sdist, which is not suggested by this RFC as some members
didn't think it's preferable in the earlier discussion.
Regarding your reference to unofficial binary gdal-wheels, As they usually
offer a binary form of the sdist I believe that it should be the equivalent
of installing the sdist (i.e. if the utils are inside the sdist then they
will be inside the unofficial binary wheels).
I do agree that all the difficulty to install the sdist from pypi (at least
on Windows) is much bigger issue that we need to address (probably by
offering binary wheels, at least for Windows) then the issue of people need
to explicitly `pip install gdal-utils` if they want the utils.
I would advise that if the PSC members think it is a good idea to remove
the utils outside the gdal sdist then maybe to add the warning in 3.3 and
to execute it in 3.5 along with the other major cleanups.

Idan

On Thu, 25 Mar 2021 at 18:46, Daniel Evans <Daniel.Evans at jbarisk.com> wrote:

> There’s also the option of using the “extra dependencies” functionality
> for Python packages, which is often used for including, well, extra
> features!
>
>
>
>
> https://setuptools.readthedocs.io/en/latest/userguide/dependency_management.html#optional-dependencies
>
>
>
> Again, it’s not entirely the intended use case – the normal use is for
> real dependencies that enable/improve functionality of the base package –
> but perhaps a bit more palatable.
>
>
>
> (I do wonder if worrying about how to tie it to the GDAL PyPI package is
> really a major point for many users, given the difficulty of installing and
> compiling it compared to the pre-compiled packages from other sources. Will
> those changes affect those distributions, too?)
>
>
>
> *Dr Daniel Evans*
>
> Software Developer
>
>
> e:  *Daniel.Evans at jbarisk.com* <Daniel.Evans at jbarisk.com>
> t:  *+44 (0)1756 799919* <+44%20(0)1756%20799919>
> *www.jbarisk.com* <http://www.jbarisk.com/>
> [image: Facebook] <https://www.facebook.com/TheFloodPeople>
> [image: LinkedIn] <https://www.linkedin.com/company/jba-risk-management/>
> [image: Twitter] <https://twitter.com/JBARisk>
> [image: YouTube]
> <https://www.youtube.com/channel/UC0iatom2jYbW96voW0rlpCw>
>
>
> All JBA Risk Management's email messages contain confidential information
> and are intended only for the individual(s) named. If you are not the named
> addressee you should not disseminate, distribute or copy this e-mail.
> Please notify the sender immediately by email if you have received this
> email by mistake and delete this email from your system.
> JBA Risk Management Limited is registered in England, company number
> 07732946, 1 Broughton Park, Old Lane North, Broughton, Skipton, North
> Yorkshire, BD23 3FD, England.
>
> *From:* gdal-dev <gdal-dev-bounces at lists.osgeo.org> *On Behalf Of *Idan
> Miara
> *Sent:* 25 March 2021 16:32
> *To:* Alan Snow <alansnow21 at gmail.com>
> *Cc:* gdal dev <gdal-dev at lists.osgeo.org>
> *Subject:* Re: [gdal-dev] Motion: RFC 78: gdal-utils package
>
>
>
> Hi Alan,
>
>
>
> pip install gdal-utils
>
> Will install also gdal as it is its dependency.
>
>
>
> In case we will take the utils out of the gdal sdist - Even tough your
> suggestion to add gdal-utils as a dependency to gdal would make `pip
> install gdal` to also install both, it makes less sense to me as gdal does
> not actually depend on gdal-utils and it might complicate things in other
> ways. In that case, IMHO telling people who want to install the utils to
> pip install gdal-utils makes more sense...
>
>
>
> Idan
>
>
>
> On Thu, 25 Mar 2021, 16:50 Alan Snow, <alansnow21 at gmail.com> wrote:
>
> > Removing the utils from the gdal sdist/wheel means that people who
> install gdal won't have the utils unless they installed the utils wheel.
>
>
>
> You mentioned that gdal_utils is now on pypi. Are you able to set it as a
> dependency in the setup.py so it is installed when the main osgeo/gdal
> python package is installed?
>
>
>
> Best,
>
> Alan
>
>
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20210326/238b2460/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image429892.png
Type: image/png
Size: 9886 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20210326/238b2460/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image302987.png
Type: image/png
Size: 651 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20210326/238b2460/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image207250.png
Type: image/png
Size: 715 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20210326/238b2460/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image972005.png
Type: image/png
Size: 966 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20210326/238b2460/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image431562.png
Type: image/png
Size: 784 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20210326/238b2460/attachment-0009.png>