Re: Defaulting to use BigAutoField in models

> > I think special casing the migrations framework is an avenue to explore, > so I created this today and to my surprise it seems to work quite well: > https://github.com/orf/django/commit/0a335f208cee1376c25eff55c6f866de122c7839 > . That is a pretty neat solution. I think it would work quite we

Re: HttpResponse headers interface

I have also found this a little odd when writing tests. It would certainly make it easier to write both normal Django code and tests, and it's a small addition, so +1 from me. On Wed, 17 Jun 2020 at 15:35, Tom Carrick wrote: > I don't find myself using HttpResponse very often, usually I'm using

Re: Proposal: Drop dependency on pytz in favor of zoneinfo

I'm almost exclusively a lurker on this list, but a constant user, and have in the past a keen observer in the datetime discussions. I think you've made your case well. I'd be happy for this migration from Django to be as aggressive as the maintainers are comfortable. I agree that doing step 1 at

HttpResponse headers interface

I don't find myself using HttpResponse very often, usually I'm using DRF's Responses. But today I needed to use one, and as I was writing tests, I ended up somewhat astonished, so with the principle of least astonishment in mind... I had anticipated that I could check the headers with `response.hea

Proposal: Drop dependency on pytz in favor of zoneinfo

Greetings all, Now that PEP 495 (the fold attribute, added in Python 3.6) and PEP 615 (the zoneinfo module, added in Python 3.9) have been accepted, there's not much reason to continue using pytz, and its non-s

Re: Defaulting to use BigAutoField in models

I think we should re-open ticket 31007[1] as there was a consensus in 2017 during the previous attempt at this[2] and things have not really changed - a 32bit primary key is still not a sensible default given the calamity that can occur when you hit the end of it’s range. The sticky point is t

contrib.auth.Group comment

Auth Groups are fabulous for designing access control into a project. However, success in such design relies heavily on either user memory or documentation. In my case it has to be documentation. To that end I believe the contrib.auth.Group model needs a comment field. That would let busines