On Thursday, 3 May 2018 05:27:11 UTC+1, Josh Smeaton wrote:
>
> As Jacob mentioned, CSP can be quite scary, and sounds like something a
> novice could try to implement for "good security" and end up causing way
> more issues.
>
Perhaps documenting some of the new (and more accessible) CSP
Thank you for looking into this!
Another benefit alongside ease of install and discoverability, is that it
makes the requirements files of projects using Django more self-documenting
(in that it avoids stray dependency entries that appear to be unused, but
actually aren't - and so need a
On Saturday, 10 June 2017 10:33:35 UTC+1, Claude Paroz wrote:
>
> Another idea is to leverage the system check framework (--deploy part) to
> warn when the max id is over 50% of available range.
>
I was about to suggest the same. Seems like something worth doing
regardless of whether we change
I agree - #24082 is unrelated since it's PostgresSQL and text field
specific, presumably resulting from:
https://github.com/django/django/blob/8eb56f3c786b4dd7f78a60145ae2e483e24b62c1/django/db/backends/postgresql/schema.py#L34-L48
The issue in this thread is specific to the interaction between
This was filed as https://code.djangoproject.com/ticket/27537 , but moving
here for discussion.
We have the following use case:
* An app uses a VM for the local development environment (eg via Vagrant).
* It's required to be accessible from the VM host (either on it's own IP,
or on localhost
