+1
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/Xn1dFyUtjJsJ.
To post to this group, send email to django-developers@googlegroups.com.
To
On Sun, Nov 27, 2011 at 4:17 PM, Jamie Matthews wrote:
> > 2. Improve the default HTTP HEAD handler by ensuring it has a blank body,
> > as this is the expectation of a response to a HEAD request. Also, there
> > should be consideration for the GET handler not existing,
> 2. Improve the default HTTP HEAD handler by ensuring it has a blank body,
> as this is the expectation of a response to a HEAD request. Also, there
> should be consideration for the GET handler not existing, which should
> result in a 405. The code appears to assume it exists, which would result
On Nov 27, 2:10 pm, Kiril Vladimirov wrote:
> Have you made some sort of TODO list I could use?
> Or selecting some failing test and make it run fine would be fine as well?
I would say: just clone the repo, try to reproduce the results, report
any differences you find from my
Hi all,
I've been playing around this the branch on github for a while now,
but unfortunately me knowledge of Django's internals only goes so far
with regards to getting multiple instance support working fully,
particularly around how models work. I've got to the point where you
can now
+1
I've often wondered why fieldsets have been possible in the Django
admin interface for a while now, but not possible with ModelForms.
Looking forward to this.
On Nov 27, 12:43 am, Mikołaj Siedlarek wrote:
> Hi,
>
> I've just posted a new ticket with everything the feature
Have you made some sort of TODO list I could use?
Or selecting some failing test and make it run fine would be fine as well?
Also, how about moving this project to GitHub?
Django is there, too(https://github.com/django/) and I thing we could find
more participants.
--
You received this