I found that in django development server , the data posted with PUT method
can't be accessed using request.POST . While it's ok with apache !
So I made a little change to django/core/handlers/wsgi.py , I've changed
line 110 to :
if self.method in ['POST', 'PUT']:
Maybe we should change
So I've been poking around in the newforms code, and it appears that
the pre-defined widgets will be producing XHTML-style output.
Now, I'm pretty picky about my markup, and I'm certainly willing to go
to unusual lengths to get it just the way I want it, but it'd be
awfully nice if there were
On 12/4/06 3:30 PM, DavidA wrote:
> I think it quickly gets more complicated than that syntax would
> support.
Oh, of *course* it does -- that's why I want to discuss it more!
I think, though, that we should be able to find a 80/20 point for aggregates
and support most of the common use
Jacob Kaplan-Moss wrote:
> No, I think not -- I think that syntax (``queryset.groupby(field).max()``)
> actually looks like the best proposal for aggregates I've seen thus far...
>
> Thoughts, anyone?
>
> Jacob
I think it quickly gets more complicated than that syntax would
support. For
On 12/4/06 5:57 AM, John Lenton wrote:
> The "max", "min" and other such functions might be a little more
> problematic, unless groupby returned, rather than a generic iterator,
> a special "queryset group" and give _it_ the max/min/etc methods. This
> way it would be clear that max() returns a
as_dl() gets a +1 from me. I've used definition lists for forms and prefer
it over tables. :)
Lakin
On 12/1/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
>
> On 12/1/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> > I agree that laying out a form with CSS is not a very clean thing. But
> > it
Hello django developers.
Currently, FIleField and ImageField store file-system-safe file name.
Imagine, if user upload a file named é.txt.
Yes, File-system-safe file name is .txt or _.txt.
It's not special case in Japan.
I know Django says non dynamic contents should be served via apache-ish
