Re: default values on database level

Hi everybody, Waking this up again because, going over some older stuff, I found a ticket asking for this feature: https://code.djangoproject.com/ticket/470 It was closed wontfix, but if anybody likes to put a 3-digit-numbered Django bug under their belt, it's there. The discussion in this thr

Re: Feedback on improving GeoDjango docs

Great to hear, GeoDjango documentation has always seemed half-finished to me, and only useful to people who are already familiar with GIS terminology. Based on my impressions from various forum posts over the years, beginners who are looking at GeoDjango: * Have never heard about OGC geometries,

Vendoring multipledispatch

Hi, On last DjangoCon sprints I started working on ticket #26355 , WIP is at https://github.com/django/django/pull/6395. During the implementation I've realized that I need a double-dispatch mechanism for registering overloaded operators. Current ap

Re: Vendoring multipledispatch

> On Apr 4, 2016, at 7:50 AM, Michał 'Khorne' Lowas-Rzechonek > wrote: > > So, I think I'm left with two options: reinvent > https://pypi.python.org/pypi/multipledispatch, or import that into > django.utils along with the license etc. > Without looking at this specific thing too closely, ma

Re: utils.suppress_warning, TestCase.assertWarns

I think django.test.ignore_warnings may meet your needs. As for the latter idea, unless something is really eager to add a Python 2 compatible version (if possible) to Django's SimpleTestCase, we can wait until dropping Python 2 support and then use the TestCase.assertWarns() in Python 3.2+. O

Re: Feedback on improving GeoDjango docs

I'm not sure about expanding and/or splitting the platform-specific instructions. These are not so well maintained and might be better suited for some wiki pages or something, e.g. https://code.djangoproject.com/ticket/25633. On Monday, April 4, 2016 at 7:10:03 AM UTC-4, Mattias Linnap wrote: >

Re: utils.suppress_warning, TestCase.assertWarns

On Monday 04 April 2016 18:37:39 Tim Graham wrote: > I think django.test.ignore_warnings may meet your needs. > Yes, probably. I had misunderstood the warnings.catch_warnings() documentation (and might have misunderstood the django.test.ignore_warnings documentation as well, if there was such d

Re: Vendoring multipledispatch

On Monday, April 4, 2016 at 3:58:09 PM UTC+2, Donald Stufft wrote: > > Without looking at this specific thing too closely, maybe it’s time for > Django to gain a required dependency instead of bundling or reinventing > everything? > +I_do_not_know_how_much -- You received this message beca

Re: Vendoring multipledispatch

+1 to allowing dependencies. For multipledispatch, I'd like to first verify the following items: 1. Does the author consider the API for multipledispatch stable? 2. Are the rules in multipledispatch what we want? If we vendor it, we can easily change the matching rules. On Tue, Apr 5, 2016 at