Re: Process DEP for "official" non-core projects

Good point. I'll get a proper DEP draft written up for next week and then we can comment on it directly with more substance - it sounds like the idea of having one is popular, though, which is what I mainly wanted to check! Andrew On Thu, May 12, 2016 at 12:52 PM, Marc Tamlyn wrote: > I'm a big

Re: Help Text Per Model Field Choice

Choices are currently very simple in core Django. There are multiple different packages which provide alternative syntaxes or useful ideas for ext

Re: Process DEP for "official" non-core projects

I'm a big fan of pulling things into github.com/django. One other point which has been raised when I've mentioned this before is the role of the django fellow(s) with regards to these projects. This should at least be touched on in the DEP. On 11 May 2016 at 20:34, William Hakizimana wrote: > Ju

Re: Template-based widget rendering

On 05/12/2016 09:39 AM, Tim Graham wrote: > So this discussion doesn't stall the rest of the patch, I suggest > keeping the fallbacks for now and deprecation them later if they cause > confusion or other problems. Yes, I think that makes sense. Carl -- You received this message because you are

Re: Admin Themes in 1.10

Seems okay to me. On Sunday, May 8, 2016 at 11:19:43 AM UTC-4, David Sanders wrote: > > 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

Re: Unicode normalization for username field

Just to be sure, do you mean django.db.migrations (referencing the appropriate validator in the migration file, I guess?) or some problem a project would face when migrating from Python 2 to 3? On Monday, May 9, 2016 at 4:00:27 PM UTC-4, Claude Paroz wrote: > > Le lundi 9 mai 2016 14:48:06 UTC+2

Re: Template-based widget rendering

So this discussion doesn't stall the rest of the patch, I suggest keeping the fallbacks for now and deprecation them later if they cause confusion or other problems. On Wednesday, May 11, 2016 at 2:08:31 PM UTC-4, Carl Meyer wrote: > > On 05/11/2016 11:52 AM, Carl Meyer wrote: > > On 05/11/2016