New feature: HTTP OPTIONS and improved HEAD for View

2011-11-26 Thread Steven Cummings
I'd like to propose some simple improvements to django.views.generic.base.View: 1. To complement the automatic HTTP 405 response, provide a default implementation of the HTTP OPTIONS method. This default response would have an HTTP 204 NO CONTENT status and include an Allow response header just li

New feature: Defining fieldsets in form class (Ticket #17301)

2011-11-26 Thread Mikołaj Siedlarek
Hi, I've just posted a new ticket with everything the feature proposal needs - motivation, idea and actual implementation. https://code.djangoproject.com/ticket/17301 It definitely needs some discussion, so please -- ask, discuss, criticize, share some thoughts and one day, hopefully +1. :) T

Re: Update on Ticket #16891: Delete/update should return number of rows modified

2011-11-26 Thread Steven Cummings
Okay, that's good stuff. So make the QuerySet APIs consistent (delete/update should return the same sort of info) but leave Model alone entirely. -- Steven On Sat, Nov 26, 2011 at 3:58 PM, Florian Apolloner wrote: > I think it would be great if delete would return the deleted rows (but > only of

Re: Update on Ticket #16891: Delete/update should return number of rows modified

2011-11-26 Thread Florian Apolloner
I think it would be great if delete would return the deleted rows (but only of the base table obviously), -1 on model.save() returning a rowcount. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on

Re: Update on Ticket #16891: Delete/update should return number of rows modified

2011-11-26 Thread Steven Cummings
Right, let me rephrase that as just Model.save(), Model.delete(), & QuerySet.delete() -- Steven On Sat, Nov 26, 2011 at 3:37 PM, Florian Apolloner wrote: > Hi, > > > On Saturday, November 26, 2011 9:42:38 PM UTC+1, Steven Cummings wrote: >> >> So, what are core-dev thoughts on going on ahead and

Re: Update on Ticket #16891: Delete/update should return number of rows modified

2011-11-26 Thread Florian Apolloner
Hi, On Saturday, November 26, 2011 9:42:38 PM UTC+1, Steven Cummings wrote: > > So, what are core-dev thoughts on going on ahead and returning > row-modified counts from Model.save() and QuerySet.update/delete? > QuerySet.update already returns the modified row count. Cheers, Florian -- You r

Re: Update on Ticket #16891: Delete/update should return number of rows modified

2011-11-26 Thread Steven Cummings
I'm assuming there's some more work to do here, but I was hoping to get opinions from core devs on what's been discussed so far. Some of the feedback above was that because save() can only return a rows-modified count of 1 right now, that it's silly to even change. So the tentative decision is simp

Re: I've made good progress in porting Django to Python 3, and could use some help!

2011-11-26 Thread hiveNzin0
Hi, I'm just learning python at the moment to use Django so I don't have the knowledge to help you but keep up the good work. I'm looking forward to seeing the result of your work. Cheers. :) -- You received this message because you are subscribed to the Google Groups "Django developers" gro

Re: Django 1.4 roadmap

2011-11-26 Thread Aymeric Augustin
On 24 nov. 2011, at 16:53, Marcob wrote: > I realize that this is a volunteer-based project, but I was wondering > if you have any updates regarding the wiki page for the 1.4 roadmap? > (https://code.djangoproject.com/wiki/Version1.4Roadmap) Hi Marco, Unlike previous releases, Django 1.4 didn't

Re: Django 1.4 roadmap

2011-11-26 Thread Marcob
On Nov 24, 4:53 pm, Marcob wrote: > Dear Django Core Developers, > I'm big on providing feedback as I feel it contributes to the health > of valuable projects like Django. Ops... I really hope I didn't hurt anyone's feelings :-) Ciao. Marco. -- You received this message because you are subscr