typo,
TEMPLATE_STRING_IF_INVALID = ExceptionRaiser()
--
Amit Upadhyay
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To uns
On May 11, 5:09 pm, Bram - Smartelectronix <[EMAIL PROTECTED]>
wrote:
> I completely agree - for a live site, but not for development!
>
> But this could be easily solved by:
> THROW_EXCEPTION_WHEN_TEMPLATE_STRING_INVALID
> default to False
You can always do:
class ExceptionRaiser:
def __str
James Bennett wrote:
> On 5/11/07, Nic James Ferrier <[EMAIL PROTECTED]> wrote:
>> Something needs to be done though... or ongoing maintenance of Django
>> apps is going to be really hard.
>
> I haven't found it terribly hard with a little coding discipline; the
> way we've handled it is to write
Am Freitag, 11. Mai 2007 14:09 schrieb Bram - Smartelectronix:
> James Bennett wrote:
> > On 5/11/07, Bram - Smartelectronix <[EMAIL PROTECTED]> wrote:
> >> there should be a clear way to trigger exceptions when non-existing
> >> variables are added to the templates.
...
> But this could be easily
James Bennett wrote:
> On 5/11/07, Bram - Smartelectronix <[EMAIL PROTECTED]> wrote:
>> there should be a clear way to trigger exceptions when non-existing
>> variables are added to the templates.
>
> Again, the reasoning is that it's better to have an empty string (or
> TEMPLATE_STRING_IF_INVALI
On 5/11/07, Bram - Smartelectronix <[EMAIL PROTECTED]> wrote:
> there should be a clear way to trigger exceptions when non-existing
> variables are added to the templates.
Again, the reasoning is that it's better to have an empty string (or
TEMPLATE_STRING_IF_INVALID, if set) come back than to th
James Bennett wrote:
>> TEMPLATE_STRING_IF_INVALID: The zen of python: "Errors should never pass
>> silently.". I want an exception if the template can't resolve a variable.
>
> "Unless explicitly silenced." Django goes out of its way to advertise
> that certain types of template errors will resu
On 5/11/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> I can't speak for others, but I'd like to see a little more than that.
> The Wiki page about schema evolution [1] has a decent set of ideas.
> From that document, specifying raw SQL for model transforms is a
> necessary, but not sufficie
On 5/11/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 5/11/07, Nic James Ferrier <[EMAIL PROTECTED]> wrote:
> > Something needs to be done though... or ongoing maintenance of Django
> > apps is going to be really hard.
>
> I haven't found it terribly hard with a little coding discipline; the
"James Bennett" <[EMAIL PROTECTED]> writes:
> On 5/11/07, Nic James Ferrier <[EMAIL PROTECTED]> wrote:
>> Something needs to be done though... or ongoing maintenance of Django
>> apps is going to be really hard.
>
> I haven't found it terribly hard with a little coding discipline; the
> way we've
On 5/11/07, Nic James Ferrier <[EMAIL PROTECTED]> wrote:
> Something needs to be done though... or ongoing maintenance of Django
> apps is going to be really hard.
I haven't found it terribly hard with a little coding discipline; the
way we've handled it is to write the necessary SQL and commit i
"James Bennett" <[EMAIL PROTECTED]> writes:
> On 5/11/07, Thomas Guettler <[EMAIL PROTECTED]> wrote:
>> First I missing a way to sync the database with the model. The command
>> syncdb has a bad name. It should be called initdb. But you can live
>> without autosync: Redirect the output of sqlall
On 5/11/07, Thomas Guettler <[EMAIL PROTECTED]> wrote:
> First I missing a way to sync the database with the model. The command
> syncdb has a bad name. It should be called initdb. But you can live
> without autosync: Redirect the output of sqlall to a file. Update model,
> redirect the output aga
Hey Thomas,
Always interesting to hear people's first (and subsequent) impressions.
Without disputing your observations, here are some of the reasons behind
the things you've mentioned. Some are problems, some are just
differences of opinion and cases where everybody cannot be pleased,
regardless
Thomas Guettler wrote:
> Background: I develop web applications with python since 6 years.
> First with Zope, then with quixote and ZODB.
> ...
> I am sorry, but I don't like the template language. I have no problem to
> have HTML in python code.
Quixote's PTL is the best way I know of doing tha
Hi,
I learned django during the last days. Here are my impressions
and some questions.
Background: I develop web applications with python since 6 years.
First with Zope, then with quixote and ZODB.
I am missing a CurrencyField. It could be a subclass of FloatField
but with a currency symbol. (
16 matches
Mail list logo
