On Tue, Nov 16, 2010 at 1:47 PM, Simon Litchfield wrote:
> Honza's #5833 is nifty. It's a pity it missed the cut last year for
> 1.1. It's been kicking around for 3 years, and there seems to be
> plenty of similar tickets that it'd address too.
>
> Any chance for 1.3? Is it just
Russell,
Thanks for reopening the ticket. I have uploaded the documentation &
will
tackle the tests after the refactor.
Thanks again,
Kent
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
Honza's #5833 is nifty. It's a pity it missed the cut last year for
1.1. It's been kicking around for 3 years, and there seems to be
plenty of similar tickets that it'd address too.
Any chance for 1.3? Is it just the lack of tests/docs or are there
design concerns?
--
You received this message
On Tue, Nov 16, 2010 at 6:02 AM, KentH wrote:
> Hi,
>
> My ticket was closed by Pandres with the comment:
>
> Your path seems to add another way to do something that is already
> easy to do (and it's done all around in the code). It goes against the
> principle of "there should
Hi,
My ticket was closed by Pandres with the comment:
Your path seems to add another way to do something that is already
easy to do (and it's done all around in the code). It goes against the
principle of "there should be one obvious way to do it"
Great reason -- but the other path is not
On Mon, Nov 15, 2010 at 5:01 PM, DD wrote:
> I try to pass a template variable to a tag as parameter, not sure how
> it works.
>
> For instance
>
> in template html
>
> {{ question.author_id }}
>
> {% monetize_slot question.author_id "questioner" %}
>
> Here I can see the
I try to pass a template variable to a tag as parameter, not sure how
it works.
For instance
in template html
{{ question.author_id }}
{% monetize_slot question.author_id "questioner" %}
Here I can see the webpage show question.author_id as "2", but when I
try to pass it via the tag