> Thanks for this ticket/patch! Yes, some documentation would be
> fantastic and would help me understand how to use this before
> committing it to trunk. Go ahead and write those docs and append 'em
> to the ticket, if you get a chance.
I wrote up some documentation in ReST style, copying the st
Wouldn't it be easy enough to support both strings and direct
references to the views? The callable() function can check that
The logic would be something like this:
if callable(viewfunc):
viewfunc()
else:
# resolve function using the older means.
or you could just check if viewfunc wa
On 9/15/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> [I'm a leading advocate for the "give Gabor a unicode branch in svn"
> school, btw, so that you and he and others can go nuts and just do it.]
+1 on this too :)
--~--~-~--~~~---~--~~
You received this mess
I have an alternate suggestion, an expansion of malcomt's idea, rather
than changing the machinery of the current url handlers, and which
should work in your existing code. (note this is untested code, but I
believe it should work, barring any syntactical errors.)
First, we define a RestfulView
> How are you accessing the request.PUT and request.DELETE? I would think
> those have to be added to the HttpRequest object before you could use
> them in the view.
Actually, Django doesn't have any specific machinery for handling PUT
and DELETE and even more esoteric ones like PROPGET, but it'l
works here, python 2.5, linux x86_64 (gentoo)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from thi
On 10/24/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> Also, I've been mulling over the idea of requiring an account signup
> in order to post tickets and comments. Would that be worth the pain?
I'm +1 on requiring an account signup; it's irritating to make wiki
edits and append to tickets on
On 11/6/06, patrickk <[EMAIL PROTECTED]> wrote:
>
> thanks - it´s been difficult enough.
> we´re doing the latest setup right now (permissions and stuff), then
> updating to the latest version.
> it should be done within the next 2 days or so - I´ll post the URL
> here ...
>
> patrick
>
Excellent
On 11/14/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 11/14/06 6:41 PM, shaunc wrote:
> > One reason (in my opinion) for an effort on a server would be to use
> > non-blocking i/o. You'd want to also use non-blocking i/o on the
> > database side as well. Has anyone thought about that fo
On 3/18/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> Of slightly more concern to me, but related, is something Jeff Croft
> pointed out today: the next release will cause problems on Dreamhost,
> since they are using an older MySQLdb setup. Not a big deal right this
> minute -- anybody usin
ticket is here: http://code.djangoproject.com/ticket/1736
James Crasta
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@g
11 matches
Mail list logo
