I'd be +1 on this, on the condition that there be some way to supress
errors, something like this.
{% for item in list %}
{{ item.title }}
{% silent %}
{{ item.owner }}
{% endsilent %}
{% endfor %}
On May 14, 11:03 pm, "John Lenton" <[EMAIL PROTECTED]> wrote:
> On Wed, May 14, 2008 at 7:19 PM,
On Wed, May 14, 2008 at 7:19 PM, Christopher Allan Webber
<[EMAIL PROTECTED]> wrote:
>
> I'm just going to chime in here that a lot of our older apps at our
> work use Zope Page Templates.
>
> Largely we've found ZPT pages to be less pleaseant in all regards
> *excepting* the fact that they
On Wed, May 14, 2008 at 10:10 PM, Adrian R.
<[EMAIL PROTECTED]> wrote:
>
> So my plan was to create a "SQL-Model" which consists of a MySQL-Query
> to get the data but which supports the normal methods like filter()
> and extra() if possible. First I didn't want to touch the django
> sources due
I'm just going to chime in here that a lot of our older apps at our
work use Zope Page Templates.
Largely we've found ZPT pages to be less pleaseant in all regards
*excepting* the fact that they never, ever silently fail. Just as
your code fails when there's a problem, so do your templates.
Hello!
Not that I have a vote, but I do have an idea...
Ken Arnold wrote:
5. Variable lookups, and everything else, never cause render() to
fail, but insert an easy-to-catch and easy-to-bypass error string in
the output.
Thoughts?
Another option for easy-to-catch and easy-to-bypass
Hi Mike,
> http://code.djangoproject.com/ticket/7233
>
> and uploaded a test case.
I've just uploaded a patch to that ticket. Hopefully, others can
review.
-Rajesh
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Hello,
I'm experiencing some odd behavior with SMTP connections and the
functions to send mail.
The relevant settings in my settings.py:
ADMINS = (
('Florian Lindner', '[EMAIL PROTECTED]'),
)
EMAIL_HOST = "xgm.de"
EMAIL_HOST_USER = "[EMAIL PROTECTED]"
EMAIL_HOST_PASSWORD = "xxx"
I use
Hi, I like to use TEMPLATE_STRING_IF_INVALID with %s, however such usage is discouraged.
I think that in production mode it's better to put no item into HTML
instead of 500 error in most of cases.
But there might be a method to mail admins somehow for important
fields having broken.
If
On May 14, 2008, at 12:29 PM, J. Cliff Dyer wrote:
>
> On Wed, 2008-05-14 at 19:00 +0400, Ivan Sagalaev wrote:
>> Simon Willison wrote:
>>> {{ article.something.title }} - outputs text if article is there,
>>> fails silently otherwise
>>>
>>> Which leaves us in a tricky situation. A global
Narendra,
On Wed, 14 May 2008, narendra.tumkur wrote:
> Hi guys,
> Trying to edit django code and keep running into indentation problems.
> Have tried XCode, Textmate and JEdit on Mac OS X.
>
> What do you guys use?
I use vim - console, not GUI.
Kevin
http://www.RawFedDogs.net
On Wed, 2008-05-14 at 19:00 +0400, Ivan Sagalaev wrote:
> Simon Willison wrote:
> > {{ article.something.title }} - outputs text if article is there,
> > fails silently otherwise
> >
> > Which leaves us in a tricky situation. A global settings.py variable
> > for "throw errors on missing
Simon Willison wrote:
> Silent errors are bad. If we were to remove them, how much of a
> negative impact would it have on the existing user base?
+1 from me.
I always set TEMPLATE_DEBUG to True and TEMPLATE_STRING_IF_INVALID to
something that stands out, during development.
--
Nicola Larosa -
On 14 Mai, 17:44, "Scott Moonen" <[EMAIL PROTECTED]> wrote:
> Adrian, disregard my previous question (you're using your own paginator).
>
> Does your paginator use len(set) or does it use set.count() to determine the
> number of items? You should find that the latter has much better
>
Apologies.
But thanks that worked.
On May 15, 1:45 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On Wed, May 14, 2008 at 10:31 AM, narendra.tumkur
>
> <[EMAIL PROTECTED]> wrote:
>
> > Hi guys,
> > Trying to edit django code and keep running into indentation problems.
> > Have tried XCode,
Adrian, disregard my previous question (you're using your own paginator).
Does your paginator use len(set) or does it use set.count() to determine the
number of items? You should find that the latter has much better
performance.
-- Scott
On Wed, May 14, 2008 at 11:36 AM, Adrian R. <[EMAIL
I like the filter idea -- maybe something like 'required' It could be
similar to marking things as safe for the autoescaping.
Default behavior should be silent failures, and authors can explicitly
set variable calls to fail visibly.
So with Simon's original example, the template author
On 14 Mai, 16:36, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> On May 14, 2008, at 9:26, "Adrian R." <[EMAIL PROTECTED]>
> wrote:
>
> > the problem is as faras I understood it, that the view is first
> > processed completely in the
> > database before it returns the result-slice. So it takes as long
Hi guys,
Trying to edit django code and keep running into indentation problems.
Have tried XCode, Textmate and JEdit on Mac OS X.
What do you guys use?
Cheers
Narendra
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Simon Willison wrote:
> {{ article.something.title }} - outputs text if article is there,
> fails silently otherwise
>
> Which leaves us in a tricky situation. A global settings.py variable
> for "throw errors on missing template variables" is a bad idea as it
> kills application portability
It
On Wed, May 14, 2008 at 10:26 AM, Adrian R. <[EMAIL PROTECTED]>
wrote:
> On 14 Mai, 16:18, "Scott Moonen" <[EMAIL PROTECTED]> wrote:
> > Adrian, are you displaying all 30,000 entries on the same page? Or are
> you
> > using some sort of pagination?
>
> No, they aren't on the same page and I'm
I made some comments on bug #5140 a while back, before I realized that
bug reports weren't a great place to discuss important things. That
bug bit me quite enough back in the early days of my project.
I'd definitely want to know if any url templatetag failed. And
probably any variable lookup
On Wed, May 14, 2008 at 10:10 AM, Deryck Hodge <[EMAIL PROTECTED]> wrote:
>
> On Wed, May 14, 2008 at 9:07 AM, Simon Willison <[EMAIL PROTECTED]> wrote:
> > Which leaves us in a tricky situation. A global settings.py variable
> > for "throw errors on missing template variables" is a bad idea
On May 14, 2008, at 9:26, "Adrian R." <[EMAIL PROTECTED]>
wrote:
> the problem is as faras I understood it, that the view is first
> processed completely in the
> database before it returns the result-slice. So it takes as long as it
> takes without a LIMIT or WHERE. That's the reason why
On 14 Mai, 16:18, "Scott Moonen" <[EMAIL PROTECTED]> wrote:
> Adrian, are you displaying all 30,000 entries on the same page? Or are you
> using some sort of pagination?
No, they aren't on the same page and I'm using pagination (and the
result can be filtered by different fields), but the
On Wed, May 14, 2008 at 10:07 AM, Simon Willison
<[EMAIL PROTECTED]> wrote:
>> I suspect that a lot of people actually rely on this behavior, and it
>> would be devastating to them.
>
> Thinking about it some more you're right - I'm sure there are lots of
> cases where people are relying on
Adrian, are you displaying all 30,000 entries on the same page? Or are you
using some sort of pagination?
-- Scott
On Wed, May 14, 2008 at 10:10 AM, Adrian R. <[EMAIL PROTECTED]>
wrote:
>
> Hello Django developers,
>
> I'm new to this mailing list and I hope that I didn't fail completely
>
Hello Django developers,
I'm new to this mailing list and I hope that I didn't fail completely
by searching the django groups while I was considering to discuss this
on the list:
At the moment (like since 1.5 years) I'm working on a web interface
which is used to control some options for a
On Wed, May 14, 2008 at 9:07 AM, Simon Willison <[EMAIL PROTECTED]> wrote:
> Which leaves us in a tricky situation. A global settings.py variable
> for "throw errors on missing template variables" is a bad idea as it
> kills application portability (the PHP magic_quotes problem again - if
> your
On May 14, 3:02 pm, George Vilches <[EMAIL PROTECTED]> wrote:
> On May 14, 2008, at 9:58 AM, Simon Willison wrote:
> > Silent errors are bad. If we were to remove them, how much of a
> > negative impact would it have on the existing user base?
>
> I suspect that a lot of people actually rely on
On May 14, 2008, at 9:58 AM, Simon Willison wrote:
> Silent errors are bad. If we were to remove them, how much of a
> negative impact would it have on the existing user base?
I suspect that a lot of people actually rely on this behavior, and it
would be devastating to them. What I've
Hi all,
Some time in late 2003, Adrian and I decided that errors in templates
were best handled silently - the idea was that it would prevent
untrained template editors from being able to 500-error a site with a
typo.
Is it too late to reconsider this decision, four and a half years
later? I
31 matches
Mail list logo
