#32544: Add support for GDAL 3.2 and GEOS 3.9.
-----------------------------------+------------------------------------
     Reporter:  Sebastian Kapunkt  |                    Owner:  nobody
         Type:  New feature        |                   Status:  new
    Component:  GIS                |                  Version:  4.0
     Severity:  Normal             |               Resolution:
     Keywords:                     |             Triage Stage:  Accepted
    Has patch:  0                  |      Needs documentation:  0
  Needs tests:  0                  |  Patch needs improvement:  0
Easy pickings:  0                  |                    UI/UX:  0
-----------------------------------+------------------------------------

Comment (by Aapo Rista):

 I guess this is not related to GEOS or GDAL versions, but M1 CPU
 architecture and the bug is in GEOS. See #32600.

 I've in this Macbook Pro (13-inch, 2017, Intel Core i5) software listed
 below and I've no problems with multi geometries.


 {{{
 $ python manage.py shell
 Python 3.9.2 (default, Feb 24 2021, 13:26:09)
 [Clang 12.0.0 (clang-1200.0.32.29)] on darwin
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> from django.contrib.gis.geos import MultiPolygon
 >>> MultiPolygon()
 <MultiPolygon object at 0x1057ab490>
 }}}

 My new Macbook Air (M1, 2020) throws Segmentation fault 11 (as seen in
 #32600).

 $ geos-config --version
 3.9.1

 $ gdalinfo --version
 GDAL 3.2.2, released 2021/03/05

 $ python -V
 Python 3.9.2

 $ uname -a
 Darwin mymac.local 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 21
 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32544#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/074.560bcd1b09d7ae54fdd431850e10693c%40djangoproject.com.

Reply via email to