#3888: Allow {# comment #} tag to be multiline
-----------------------+----------------------------------------------------
   Reporter:  tonnzor  |                Owner:  adrian         
     Status:  closed   |            Component:  Template system
    Version:  SVN      |           Resolution:  wontfix        
   Keywords:           |                Stage:  Unreviewed     
  Has_patch:  0        |           Needs_docs:  0              
Needs_tests:  0        |   Needs_better_patch:  0              
-----------------------+----------------------------------------------------
Changes (by [EMAIL PROTECTED]):

 * cc: [EMAIL PROTECTED] (added)

Comment:

 I just want to reply to this issue to say that we've been bitten by this
 problem too. We have a policy to always include a header in our files so
 we have something like this in our templates:
 
 {{{
 {#
  # NAME
  #    $HeadURL$
  # DESCRIPTION
  #    This template is used to foo the bar.
  # COPYRIGHT
  #    Copyright (C) 2007 Baz
  # VERSION ID
  #    $Id$
  #}
 }}}
 
 This code is accepted by the parser (no errors or exceptions). This
 however has the nasty side-effect of eating up all content upto the next
 tag. Using this (which we had before):
 
 {{{
 {% comment %}
 # NAME
 #    $HeadURL$
 # DESCRIPTION
 #    This template is used to foo the bar.
 # COPYRIGHT
 #    Copyright (C) 2007 Baz
 # VERSION ID
 #    $Id$
 {% endcomment %}
 }}}
 
 causes weird problems with the {{{ {% extends %} }}} tag (which must be
 the first tag).
 
 Is there an acceptable way to include a standard documentation/copyright
 header?

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3888#comment:9>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to