Re: Potential Bug in django.contrib.gis

Additional Info: I get this behavious in python 3.6.7, which according to the documentation should be compatible with django 3.1. Janis schrieb am Donnerstag, 3. September 2020 um 17:16:50 UTC+2: > > Hi all, > I recently upgraded django 1.11 to 3.1. Now, in dango 3.1, the following

Potential Bug in django.contrib.gis

.6, 0.4), (0.4, 0.4)) >>> poly = Polygon(ext_coords, int_coords) >>> next(poly[0].__iter__()) Segmentation fault (core dumped) Is this a bug or might there be another reason (e.g. hardware-related issue)? Thanks, Janis -- You received this message because you are subscribed t

django-nani usage

Hello, Does anyone use django-nani for model translations? I'm a newbie to django, and my question is: How do you switch languages in after you've set up your translations with django-nani? Do I have to set up a url in urls.py with language codes in it, and then in corresponding view filter my data