I'll note that gdal 3.3.1 is not officially supported (cf
https://docs.djangoproject.com/en/3.2/ref/contrib/gis/install/geolibs/).
However, homebrew does not make it easy to install older versions of
tools.
--
Ticket URL: <https://code.djangoproject.com/ticket/32927>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => duplicate
* component: Uncategorized => Database layer (models, ORM)
* type: Uncategorized => Bug
Comment:
It's a duplicate #32600 where we believe Django is not at fault.
I also added a separate ticket to confirm support for GDAL 3.3, see
#32928.
--
Ticket URL: <https://code.djangoproject.com/ticket/32927#comment:1>
Comment (by szunami):
@Mariusz I can still reproduce this issue locally, after having just
installed django from main. Is this expected?
{{{
python
Python 3.9.6 (default, Jun 28 2021, 19:24:41)
[Clang 12.0.5 (clang-1205.0.22.9)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import django
>>> django.get_version()
'4.0.dev20210719094220'
>>> from django.contrib.gis.geos import Polygon, MultiPolygon
>>> MultiPolygon(
... Polygon(((-10, 10), (-10, -10), (10, -10), (10, 10), (-10, 10)))
... )
[1] 5688 segmentation fault python3
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32927#comment:2>
Comment (by Mariusz Felisiak):
If you have any additional details, please add a comment to the #32600,
see also comments [https://code.djangoproject.com/ticket/32600#comment:2
2] and [https://code.djangoproject.com/ticket/32600#comment:3 3].
Currently we cannot prove that Django is at fault.
--
Ticket URL: <https://code.djangoproject.com/ticket/32927#comment:3>