Hi Russell,
> However, it does need to have it's UX issues sorted out. The most
> recent substantive comment on the ticket [1] indicates that the patch
> isn't ready for checkin. It also suggests that there are broader
> improvements that may need consideration. To the best of my knowledge,
> nobo
I guess it may just be helpful to at least fix the 'for current
documentation' links on these pages:
http://www.djangoproject.com/documentation/0.96/model-api/
just to go to http://docs.djangoproject.com in general, even if it's not the
correct place, it's better than a message going to the wrong p
On Thu, Jul 22, 2010 at 4:30 AM, Russell Keith-Magee
wrote:
> I accept the need for this, but this seems like a bit of a wart. This
> method wouldn't be required at all if the Form took a request
> argument. This isn't an unusual requirement, either -- perhaps we
> should introduce a RequestForm/R
Hi all,
brand new django contributor here, been using it so much I reckon it's
about time I started giving back :)
Anyhow, I'm using Django primarily to develop RESTful API's for web
services. This of course means a lot of JSON is getting passed around
in GET/POST requests so I wrote a simple for
On Sat, Aug 14, 2010 at 1:39 PM, burc...@gmail.com wrote:
> I had few useful thoughts about changing the way Django development
> contributions gets accepted and committed -- but all I get from this
> mailing list that all attempts to improve any process is just a waste
> of time.
That's not enti
