If a user write in a field and solve eliminate this inline form, I need to
clear all fields using javascript to view ignore this form. It would be
better if there was an option to mark the inlineform that will be ignored,
that would be much simpler.
In my form, all fields are required, I think
Hi Paulo,
On Sat, Mar 28, 2015 at 8:12 AM, Paulo Maciel
wrote:
> I started working with formset and found half cast, for example, when
> configuring a formset with min_num = 1, django requires that the first form
> of the formset (form-0) is completed, I see this as a bug, it should check
> for
I started working with formset and found half cast, for example, when
configuring a formset with min_num = 1, django requires that the first form
of the formset (form-0) is completed, I see this as a bug, it should check
for some form completed and validated, should not require that the form-0
Sounds broadly good to me. I'd be happy for it to be pushed to pypi under
django-legacy or similar name.
Marc
On 27 Mar 2015 16:36, "Tim Graham" wrote:
> Sounds good to me.
>
> On Friday, March 27, 2015 at 12:28:09 PM UTC-4, Carl Meyer wrote:
>>
>> Hi Christian,
>>
>> On 03/26/2015 05:11 PM, Chr
Sounds good to me.
On Friday, March 27, 2015 at 12:28:09 PM UTC-4, Carl Meyer wrote:
>
> Hi Christian,
>
> On 03/26/2015 05:11 PM, Christian Hammond wrote:
> > I know you guys are still sorting out how you want to run this, but I
> > wanted to let you know that, given our current dependence on
Hi Christian,
On 03/26/2015 05:11 PM, Christian Hammond wrote:
> I know you guys are still sorting out how you want to run this, but I
> wanted to let you know that, given our current dependence on Python 2.6,
> I'm willing to do what's needed to maintain security backports for
> either an officia
Hi John and Christian,
On 03/27/2015 09:46 AM, John Paulett wrote:
> James, thanks for putting this together.
>
> Christian, I am in a similar position, supporting 2.6 for the next 6-12
> months. I had planned to keep a personal fork of Django 1.6,
> backporting security patches as needed, but I
James, thanks for putting this together.
Christian, I am in a similar position, supporting 2.6 for the next 6-12
months. I had planned to keep a personal fork of Django 1.6, backporting
security patches as needed, but I would be happy to contribute to a common
effort in this regard.
As mentioned
Instructions for requesting to be added to the security prenotification
list are here:
https://docs.djangoproject.com/en/dev/internals/security/#requesting-notifications
On Thursday, March 26, 2015 at 7:11:12 PM UTC-4, Christian Hammond wrote:
>
> Hi Carl, James,
>
> Sorry for the late reply on
