Re: Template Engine Compilation and Runtime Refactoring Progress

[Aymeric Augustin]

On 19 juin 2011, at 12:39, Anatoly Vostryakov wrote:
>  Ok. Thanks for answer. I'll think to add support of parameters to
> functions in django template engine after GSOC. From my point of view
> it is
> backward compatible feature. All old django templates will continue to
> work.

Hi Anatoly,

Before working on a patch, you'll probably want to check the mailing list 
archives and bug tracker, as this feature has been discussed and rejected in 
the past.

The last paragraph of 
https://docs.djangoproject.com/en/dev/topics/templates/#accessing-method-calls 
explains why.

Best regards,

-- 
Aymeric Augustin.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

[GSoC composite fields] Another weekly check-in

[Michal Petrucha]

Another weekly update.

First off, I'd like to apologize for not posting one last week; I've
been completely buried under exams and other school-related stuff
during the past three weeks...
Things have settled now at last so I'm back at my SoC and cathing up.

My repo [1] now contains support for index creation over
CompositeFields and the ``unique`` attribute just results in the
fields being added to the ``unique_together`` model option.

About the code that generates the CREATE INDEX SQL, though, I haven't
found any way to properly test that (the tests usually don't mess with
backend-dependent SQL code). I'd expect there are some tests for this,
it's just that I haven't found them yet. I'd appreciate any pointers
in the right direction.

Slightly off-topic: I'm using rebases in my repo, mainly to see my set
of changes on the top (and not scattered around the history). Is it
okay if I continue using them or am I complicating someone else's work
with this?

Michal

[1] https://github.com/konk/django


signature.asc
Description: Digital signature

Re: Template Engine Compilation and Runtime Refactoring Progress

[Anatoly Vostryakov]

Hi!

> The compiler is able to handle this case, but the syntax of the Django
> templating language does not.  I will not change any features in the
> Django template engine during this proposal and actually reused most
> of the parser toolchain until fall.  If someone wants to step up and
> continue improving the features on the language after GSOC I am happy
> to assist.

  Ok. Thanks for answer. I'll think to add support of parameters to
functions in django template engine after GSOC. From my point of view
it is
backward compatible feature. All old django templates will continue to
work.

Regards,
Anatoly

On Jun 18, 7:52 pm, Armin Ronacher 
wrote:
> Hi,
>
> On Jun 17, 2:18 pm, Anatoly Vostryakov  wrote:>   
> I've thought today. May be it will possible to add support of
> > parameters for functions or object methods in django templates.
> > I mean, something like this in django template:
>
> The compiler is able to handle this case, but the syntax of the Django
> templating language does not.  I will not change any features in the
> Django template engine during this proposal and actually reused most
> of the parser toolchain until fall.  If someone wants to step up and
> continue improving the features on the language after GSOC I am happy
> to assist.
>
> Regards,
> Armin

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Logging configuration and handle_uncaught_exception

[Carl Meyer]

In case anyone's interested in this but isn't following the ticket,
I've attached an updated patch there using a variant of Vinay's
suggestion, and with some shim code to address backwards-compatibility
concerns. Reviews welcome.

Ticket is at https://code.djangoproject.com/ticket/16288

Carl

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.