Hi Maximiliano,
Sorry for the delay in responding to this.
On Thursday 22 May 2014 17:06:23 Maximiliano Robaina wrote:
> El jueves, 22 de mayo de 2014 03:24:12 UTC-3, Shai Berger escribió:
> >
> > Quoting it uncoditionally would break the test on Oracle (which, by
> > default, turns all the name
If we did split it out, would you be interested in being a maintainer?
On Monday, May 26, 2014 6:51:13 PM UTC-4, Gordon wrote:
>
>
>
> On Monday, May 26, 2014 6:04:31 PM UTC-4, Tim Graham wrote:
>>
>> My observation is that not many core developers seem interested in
>> contrib.formtools these da
On Monday, May 26, 2014 6:04:31 PM UTC-4, Tim Graham wrote:
>
> My observation is that not many core developers seem interested in
> contrib.formtools these days. It was added by Adrian in 2006, but as far as
> I can see from the commit history, it hasn't received much love lately. If
> would
My observation is that not many core developers seem interested in
contrib.formtools these days. It was added by Adrian in 2006, but as far as
I can see from the commit history, it hasn't received much love lately. If
would be a good candidate for deprecation from Django itself, in my opinion.
Hello,
I have posted an implementation/proof of concept to ticket 21644
(https://code.djangoproject.com/ticket/21644). The implementation is
currently written as a mixin because I need to be able to use it now and I
don't like maintaining a custom fork of django for my projects. If changed
t
Thanks Russ, I missed #9475 in my search. I'll have a read through those
tickets...
...and back. I'm leaning towards keeping the API as-is, with
add/create/remove simply unavailable or raising exceptions if the
intermediate model doesn't meet the requirements.
A few reasons:
1. As the discussi
