Re: [Technical Board?] Project Ideas, and beginning GSoC 2023.

Adrian, > I'd personally like to see better support for safe / N-1 compatible migrations within Django itself, currently if you do CD / blue-green tower / etc. deployments you need to be very careful about the migration operations that you introduce version-to-version, although I'm not sure wh

Re: Set a reasonable default for EMAIL_TIMEOUT

Federico - I think we’d like to see a few more “pro”s in the thread. Personally, I am pro adding a default timeout. The lack of a default timeout in *requests* is a constant source of outages, which lead me to write this hack

Re: Set a reasonable default for EMAIL_TIMEOUT

Hi everyone, do you think you are against on opening an issue for this? I had already opened an issue which was marked as wontfix and I was asked to open this discussion here. Best regards Federico On Monday, November 21, 2022 at 5:31:27 PM

Re: #21978 include production-ready web server

At Florian's suggestion in another thread, I propose that we move further discussion of the settings refactor to the forum: https://forum.djangoproject.com/t/settings-refactor/17352 On Wednesday, November 2, 2022 at 2:58:29 PM UTC-4 f.apo...@gmail.com wrote: > The speckenv example highlights t

Re: Integrate dj-database-url into Django

I started a forum thread on the settings refactor here: https://forum.djangoproject.com/t/settings-refactor/17352 Regarding the original topic of this thread ( https://code.djangoproject.com/ticket/28236), are we ready to close this as wontfix? I'm okay not proceeding with it (dj-database-url, dja

Re: [Technical Board?] Project Ideas, and beginning GSoC 2023.

I'd personally like to see better support for safe / N-1 compatible migrations within Django itself, currently if you do CD / blue-green tower / etc. deployments you need to be very careful about the migration operations that you introduce version-to-version, although I'm not sure what that wou

Re: Potential way forward for DATABASE_URL

Alright, I'm writing up a review aid that tries to re-explain the actual changes in the PR I opened before. This document should go over all of the actual API changes that are exposed to users as well. I believe the API _is_ correct, and that future settings improvements could rely on these to