Django security releases issued: 2.2.3, 2.1.10 and 1.11.22

Today the Django team issued 2.2.3, 2.1.10, and 1.11.22 as part of our security process. These releases address security issues, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2019/jul/01/security-releases/ -- You received this message because y

Django security releases issued: 2.2.3, 2.1.10 and 1.11.22

Today the Django team issued 2.2.3, 2.1.10, and 1.11.22 as part of our security process. These releases address security issues, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2019/jul/01/security-releases/ -- You received this message because y

New feature - Define a variable TESTS in settings

Hi, I think it might be useful to define a variable (such as TESTS) in settings, which will only be True when running tests, and then Django will know we are running tests and act accordingly, for example save files in a different directory (such as TESTS_MEDIA_ROOT) and not in the default MEDIA_R

Re: Fellow Reports - June 2019

Week ending June 30, 2019. *Triaged:* https://code.djangoproject.com/ticket/30586 - Django 2.2 compatibility with PyMySQL. (duplicate) https://code.djangoproject.com/ticket/30587 - Cloaking exceptions raised by get_object_or_404(). (duplicate) https://code.djangoproject.com/ticket/30588 - ipdb

Re: Fellow Reports -- June 2019

Hi All, Calendar Week 25 -- ending 23 June. Triaged: https://code.djangoproject.com/ticket/30581 -- Allow constraints to be used for validation (in Python) (Accepted) https://code.djangoproject.com/ticket/30577 -- feature request: custom rendering for readonly fields in admin (needsinfo)

Re: New feature - Define a variable TESTS in settings

Hi, I think it is better to do what Josh mentioned in https://code.djangoproject.com/ticket/30605#comment:2. To elaborate on how this looks in pratice: Write a file called ``settings_test.py`` or such, containing something like this: ``` from .settings import * DEFAULT_FILE_STORAGE = 'inmemory

Re: Discussing improvements of django.setup()

Hello Aymeric, regarding django.setup() idempotence I continued discussion in the PR. Regarding django.setup() tweakability, the generic need is simply to have a hook, somewhere for users to put early init code, regardless of the way django is launched. Code that needs to execute this early are