Re: GSoC 2020

Hi Carlton, I will start working on this. I’ll create a new thread for further correspondence. Thanks and regards, Abhirav Dilip Kariya On Fri, May 8, 2020 at 10:29 AM Carlton Gibson wrote: > Hi Abhirav. > > I think this is an interesting project. It would be nice if we had a story > for

Re: Rename request.GET and POST, and lowercase COOKIES, FILES, and META

It seems that many of the people who want a different name are not understanding that this name is going to be exclusively for dealing with POST forms that are using the standard `x-www-form-urlencoded` media type*, *and won't be attempting to interpret any other media type. Some generic names,

Re: Rename request.GET and POST, and lowercase COOKIES, FILES, and META

> On 7 May 2020, at 22:03, Florian Apolloner wrote: > > forms with method="GET" are legitimate and wouldn't end up in `form_data` > forms with method="GET" are legitimate and wouldn't end up in `form_data` > which is imo quite confusing. Do we have any other options? Would there be an issue

Re: Rename request.GET and POST, and lowercase COOKIES, FILES, and META

On Wed, 6 May 2020 at 17:49, Adam Johnson wrote: > +1 request.data >> >> We shouldn’t be POSTists, there is also PUT and PATCH. >> > > Would just like to point out - that's not the proposal. The proposal is to > rename the existing request.POST to request.form_data, which is based on > parsing

Re: Status of 3.1 release blockers.

> > I think we should also address: > > https://code.djangoproject.com/ticket/30678 > > > - GDAL 3 support > > as release blocker, because more and more installations

Re: GSoC 2020

Hi Abhirav. I think this is an interesting project. It would be nice if we had a story for handling sensitive values that went (in principle) from "use environment variables" (or a file) to the various Vault-like options. The trick is making that compelling as a feature for Django, but such a

Re: Status of 3.1 release blockers.

Hi Mariusz, I think we should also address: https://code.djangoproject.com/ticket/30678 - GDAL 3 support as release blocker, because more and more installations will have GDAL 3 by default and the backwards compatibility issues are serious. I'll try to prepare a patch ASAP. As this is only

A precise and simple version archive

Hallo Django CMS community, I'm writing a new module that creates an archive of elder page versions. We are _not_ using the Django CMS Versioning module, because we want something that combines simplicity and robustness with precision, plus, we