Jacob Kaplan-Moss

This no longer applies; could you re-merge from master please?

The book should cover the newest (1.5), and not mention the older layout. Can you update this please?

Lovely, sounds like we're thinking exactly on the same lines. Yes, I'll give this a stab and see where I can get, thanks!

Couple of quick notes from meeting with @mjtamlyn in person: - We don't have a process for updating DEP 1 (LOL) so this change should include the process by which...

Another improvement: for feature DEPs, add an "Implementation" section to the end of Final DEPs that points to the commits/PRs/etc that were merged to implement the DEP.

Hm, I'm not sure - there might be reasons that failing silently is ok. Maybe a warning, or something using the checks framework? What do other folks think?

I think a warning when `default` is given and used will become annoying, and we should avoid it. A pretty common pattern I use for local dev is: ```python DATABASES...

@mattseymour my gut reaction is that this looks pretty inelegant; I don't love cramming stuff into the URL like this, and I find turning the flat URL into a dictionary......

@Brodan I will try, no promises though. I've taken this over as an interim thing (see #120) and am not yet totally sure what my level of commitment I'm up...

@Brodan thanks for understanding. OK, I've taken a look, and this mostly looks good. I've got two small changes that I'd like to request before merging: 1. The documentation (README)...