Re: Making Django more PaaS-friendly

Whee, this thread got big! The takeaway I'm getting here is that we should be careful about what we adopt into core and when; I'm going to take a couple days and write up some notes on what I think a good conservative approach would look like, and ask for feedback on that. (spoiler: probably the

Admin Themes in 1.10

Ever since PR #5567 [1] (which is great, yay CSP) I've been concerned about the impact it will invariably have on admin themes going forward. By removing any inline JS, the various admin JS functionality is now initialized in the JS files where it is much harder to extend or change for an admin

Help Text Per Model Field Choice

Hey all, I think it would be a greatly useful feature to be able to set help text for choices on a model field. For the default Select widget this would be rendered as the title attribute for each choice, which browsers show when you hover over a choice. This also makes it simple to render the

Re: deprecating the "escape" half of django.utils.safestring (#24046)

On 05 Mar 2016, at 17:16, Tim Graham wrote: > The behavior of escape running last no matter its position doesn't seem so > intuitive That’s putting it mildly, considering that Django explicitly makes the parallel between template filters and Unix pipes. > but it could be