My only problem with this is that I feel I'm writing framework-code in
my view. I'm clearly breaking the separation between application and
framework. Of course, no design will ever be perfect and you will
always have corner cases like this.
Instead of ditching the idea alltogether I think
OK.. I gave it a shot.. not really satisfied with the patch yet, but
it's a start. Feel free to suggest improvements (or submit a better,
or extended, patch) if need be.
Here's the ticket http://code.djangoproject.com/ticket/5076
Hope everyone has a great friday!
Regards,
Daniel
On 8/2/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 8/2/07, Daniel Brandt <[EMAIL PROTECTED]> wrote:
> > I am recieving POST-data that is submitted to my application not via a
> > form or a browser, but from other web applications, according to a
>
I was cleaning up a django app to work with the unicode merge, when I
noticed a problem that has taken me a good while to debug, and I
still don't have the full picture.
I am recieving POST-data that is submitted to my application not via a
form or a browser, but from other web applications,
On 4/18/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 4/18/07, Daniel Brandt <[EMAIL PROTECTED]> wrote:
> > Something has been bugging me for a while..
>
> This type of complaint seems to come up every few months. I'm always tempted
> to
>
On 4/11/07, Brian Beck <[EMAIL PROTECTED]> wrote:
>
> I consider this a wart and it's been bugging me for a while. So,
> sparked by some discussion in #django, here goes...
>
> I'd like it if template filters supported multiple arguments for real.
> Currently filters that need multiple arguments
