Re: I would like to discuss my proposal for a working way to call .add() on an m2m with through= model

2017-03-20 Thread Collin Anderson
Hi, Check out https://code.djangoproject.com/ticket/9475 Seems like it would be fine if Django allowed add() and let any errors about missing data bubble-up. I personally think passing in a defaults dict (just like get_or_create does) would also be fine, but a callback seems like overkill.

Re: status of 1.11 release blockers

2017-03-20 Thread Tim Graham
We're not quite down with blockers -- one was reported a few hours ago, so I'm postponing the RC until tomorrow. On Saturday, March 18, 2017 at 7:49:43 PM UTC-4, Tim Graham wrote: > > A handful of blockers (mostly in the final stages) remain as of right now > [0]. We're on track to issue the

Any interest in integrating Django Admin Sortable into core?

2017-03-20 Thread Brandon Taylor
Hello Django Developers, I've been a longtime user (since before the "newforms-admin" branch) and proponent of Django and am the creator and maintainer of Django Admin Sortable: https://github.com/iambrandontaylor/django-admin-sortable I've been fortunate enough in my career to have been able

I would like to discuss my proposal for a working way to call .add() on an m2m with through= model

2017-03-20 Thread Luis Masuelli
I was reading this link in the official history and this other link in this group , but still do not understand why the issue against a way to call .add() to add a

Re: Provide forms field/widget type information for use in templates

2017-03-20 Thread Paweł Adamczak
Huh, don't know how I missed that. Thanks! In that case, I would add the information to the docs, to the ticket, and close it : -) On Monday, March 20, 2017 at 4:36:17 PM UTC, Collin Anderson wrote: > > Hi, > > If it helps It looks like there's a widget.input_type attribute, so you > can at

Re: Provide forms field/widget type information for use in templates

2017-03-20 Thread Collin Anderson
Hi, If it helps It looks like there's a widget.input_type attribute, so you can at least do {% if theform.thefield.field.widget.input_type == "checkbox" %} etc. Collin On Mon, Mar 20, 2017 at 9:46 AM, Paweł Adamczak wrote: > Hiya, > > I would like to 'resurrect' ticket

Provide forms field/widget type information for use in templates

2017-03-20 Thread Paweł Adamczak
Hiya, I would like to 'resurrect' ticket #13009 , or at least discuss it. I think that the suggested feature would be beneficial, as it comes up every time I'm implementing HTML flats different types of fields require different rendering (the most

Inconsistent Behavior in Auth with UserAttributeSimilarityValidator

2017-03-20 Thread Andrew Pinkham
Hi, I've found some inconsistent behavior in how password validation via the `UserAttributeSimilarityValidator` is handled by `contrib/auth`. I did not find any mention of this in Trac or on the mailing list, but apologies if this has already been discussed. AFAICT: When creating a user, the

Re: Permission classes for Class Based Views

2017-03-20 Thread Paweł Święcki
Good idea. I use permission classes in DRF and I would use them in Django. Using `|` for "or" is something to be discussed, though. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this

Re: Composite key development

2017-03-20 Thread Anssi Kääriäinen
Just my late 2 cents to this... First, I wouldn't put too much weight on the DEP proposals. Looking back to them now, I don't think they went to the right direction. For Michal Petrucha's work, it was really close to being merged some years ago. The problem was that migrations happened at the