On Fri, Mar 5, 2010 at 2:54 PM, Jonathan S wrote:
> Just a few thoughts, this is my idea and I'm not an expert at
> compilers, so forgive me if I'm somewhere wrong.
>
> (1) For me, personally, I think the scoping of variables should be
> kept inside a block.
>
> {%
This is really cool, thanks for sharing it!
One small question though, would it be better to check TEMPLATE_DEBUG
instead of DEBUG -
http://docs.djangoproject.com/en/dev/ref/settings/#template-debug
?
--
--Leo
On Mar 5, 10:11 am, Jonathan S wrote:
> On Mar 5, 6:59
I've read through the history on this group about triage process and I
have an idea I'd like to offer gently:
When I'm looking for tickets to work on, I often wish there was a
triage stage between "accepted" and "ready for checkin". On other
trackers the "feedback" triage stage is for this
On Sat, Mar 6, 2010 at 3:53 AM, subs...@gmail.com wrote:
> Hello there,
>
> I'm interested in allowing a particular filter I have to check the
> context. Trolling for reasons for and against, and if it makes no
> difference I'll file a ticket and provide some patches.
Unless
Just a few thoughts, this is my idea and I'm not an expert at
compilers, so forgive me if I'm somewhere wrong.
(1) For me, personally, I think the scoping of variables should be
kept inside a block.
{% with "x" as x %}
{% with "y" as x %}
{% endwith %}
{{ x }}
- you would print "y",
Hello there,
I'm interested in allowing a particular filter I have to check the
context. Trolling for reasons for and against, and if it makes no
difference I'll file a ticket and provide some patches.
Its useful for me in cases where the thing I am processing has already
been processed before.
On Mar 5, 6:59 pm, Jared Forsyth wrote:
> On a related note, is there a way to tell templates *not* to fail silently?
> (most tags etc. do)
> for testing/debugging purposes?
I don't think that all template tags fail silently.
Lookup of variables does always fail
On a related note, is there a way to tell templates *not* to fail silently?
(most tags etc. do)
for testing/debugging purposes?
jared
On Fri, Mar 5, 2010 at 9:53 AM, Jonathan S wrote:
>
> On Mar 5, 5:49 pm, Jared Forsyth wrote:
> > I presume
although it is not the best, django is well documented imo. (my
favorite after php manual)
browsing the source is not bad at all when the documentation is not
enough for the developer. you become more familiar to the django if
you dive in to the source. it is very handy when you need some
On Mar 5, 5:49 pm, Jared Forsyth wrote:
> I presume these only get shown with DEBUG turned on?
Yes, they are only shown when DEBUG is on:
see line 163:
http://github.com/citylive/Django-Template-Tags/blob/master/templatetags/debug.py#L163
--
You received this message
Your right the docs are there and they are very useful I think. I
missed a few things when opening this ticket let me be more precise I
would like to see the module index at the top of the actually module
doc page. The module index's are offered as separate link on the docs
page which lists the
On Fri, Mar 5, 2010 at 11:35 AM, stherrien wrote:
> What I'm suggesting is that we setup something to allow everyone to
> improve the docs with help from the core django group. I think this
> would be very helpful to everyone. if one of the core group would like
> to help
I presume these only get shown with DEBUG turned on?
On Fri, Mar 5, 2010 at 9:09 AM, Jonathan S wrote:
> Hi Django users,
>
> We made at our company, City Live, a template tag you may be
> interested in.
> It's a try/catch statement. When anything in the try block
On Mar 5, 2010, at 11:35 AM, stherrien wrote:
> What I'm suggesting is that we setup something to allow everyone to
> improve the docs with help from the core django group. I think this
> would be very helpful to everyone. if one of the core group would like
> to help us get setup to do this it
On Fri, Mar 5, 2010 at 11:40 AM, Karen Tracey wrote:
> ... open a ticket and attach the patch.
>
>
And, as for all other tickets, it'll help if you search the tracker first
and make sure that whatever ticket you're planning on opening isn't already
open.
Karen
--
You
Uhh... the documentation is part of djangos repository, along with all of
the code. It has long been django's policy to treat docs contributios the
same as code contributios.
Alex
On Mar 5, 2010 11:35 AM, "stherrien" wrote:
What I'm suggesting is that we setup
The Django documentation is already included in code base with Django and
anybody is welcome to submit patches for them. If you do a checkout of
Django, there will be a "docs" directory there. Inside there is the full
documentation source in reStructuredText. If you'd like a local HTML or PDF
That's interesting, I'm of the other belief... I find the Django
documentation to be thorough and organised very well.
One of the main reasons I (and I am sure countless others) even started
using Django was because of it's excellent documentation.
As the project has matured from version 0.96
On Fri, Mar 5, 2010 at 11:35 AM, stherrien wrote:
> What I'm suggesting is that we setup something to allow everyone to
> improve the docs with help from the core django group. I think this
> would be very helpful to everyone. if one of the core group would like
> to
What I'm suggesting is that we setup something to allow everyone to
improve the docs with help from the core django group. I think this
would be very helpful to everyone. if one of the core group would like
to help us get setup to do this it would be great. maybe if they setup
a repository with
Exactly my point docs need to be more organization to be constructive
for django users.
On Mar 5, 11:05 am, Jared Forsyth wrote:
> To be honest I am quicker to just go to django's source code rather than the
> docs, as often I can find what I need there, and the docs
Hi Django users,
We made at our company, City Live, a template tag you may be
interested in.
It's a try/catch statement. When anything in the try block fails, a
traceback through all the included templates is shown.
A good approach would be to include {% try %} ... {% endtry %} in the
base
To be honest I am quicker to just go to django's source code rather than the
docs, as often I can find what I need there, and the docs aren't (imo)
organized enough to provide much of an advantage.
On Fri, Mar 5, 2010 at 8:46 AM, stherrien wrote:
> Hi all,
>
>
> I have
Hi all,
I have a request that django documentation show the import locations
for classes like in other well formed docs found on the web showing
the users where the classes can be found for import. I think this
would be handy for newer users and experienced users finding something
new.
24 matches
Mail list logo