Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

If it helps, there's a also a shortcut: ./manage.py runserver 0:8000. Much easier to type. On Mon, Nov 28, 2016 at 8:48 AM, wrote: > This was filed as https://code.djangoproject.com/ticket/27537 , but > moving here for discussion. > > We have the following use case: > * An

Re: Should SECRET_KEY be allowed to be bytes?

Hello, I saw these emails today and am finally getting around to responding to them now. I'm one of the people commenting to those issues about the SECRET_KEY being bytes and how I think it should still be allowed. I think there's a misunderstanding about what I said in those issues.

Re: Adding UNION/INTERSECT/EXCEPT to the ORM

Ok, everything seems to be working so far, I'll try adding `is_allowed` over the next few days, then I can get rid of the extra `QuerySet` class. On Friday, December 23, 2016 at 3:12:40 PM UTC+1, Florian Apolloner wrote: > > Hi, > > I have a currently WIP PR at

Re: Template-based widget rendering

I noticed that the GIS widgets didn't use the new API so I added a commit for that. I tested the widgets in the geodjango tutorial and they looked okay. I'm not sure how well those widgets are tested in Django's test suite -- if any GIS users want to review the changes and/or test the branch

Re: Should SECRET_KEY be allowed to be bytes?

On 23 Dec 2016, at 16:48, Tim Graham wrote: > also allow bytestrings (even non-ASCII bytestrings as reported in #19980?). There are arguments both ways. Allowing non-ASCII bytestring means every app that needs bytes must call force_bytes(settings.SECRET_KEY) instead of

Re: #26369: default formfield callback override

Thanks for your reply Adam ! To make it general purpose, perhaps we could make such a patch in Django and replace should_fixup by a signal ? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe

Re: Considering removing support for ("iLmsu") regex groups in URLpatterns. Do you use them?

I found a flask thread [0] where Armin Ronacher said this about case-insensitive URLs: "I think it's a horrible idea. It destroys your caching and creates multiple entries for search engines." Adam Oakman added: "Agreed. My personal method is to code the 404 handler to look for uppercase

Re: Adding UNION/INTERSECT/EXCEPT to the ORM

Hey Florian! > How can I change the generated order_by clause to reference the columns "unqualified" (ie without table name), can I somehow just realias every column? Now that we have F() aliasing working in iterator() I would suggest to restrict all combined queries to have the same set on

Re: #26369: default formfield callback override

Thanks a lot for your time and quick answer Adam ! The ModelFormMetaclass usage you suggest is not supported by Django at this point. Suggesting that doing it is easy and supported seems incorrect in my experience, starting with the fact that there is no documentation. There are a lot of problems