﻿id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc
296,py:element directive,Arc Riley <arcriley@…>,cmlenz,"Currently to generate elements from a list some hackery is needed, ie:

{{{
#!genshi
<?python from genshi.builder import tag ?>
<py:for each='field in fields'>
  ${getattr(tag,field)}
</py:for>
}}}

It would be cleaner if we could instead:

{{{
#!genshi
<py:for each='field in fields'>
  <py:element name=""field""/>
</py:for>
}}}

`py:attrs` should be applied second such that:

{{{
#!genshi
<py:for each='field in fields'>
  <py:element name='field' py:attrs='fields[field]'/>
</py:for>
}}}

It would be useful if the element name could contain the namespace, ie:

{{{
#!python
fields = {'greek:alpha' : {'value' : 1, 'xmlns:greek' = 'xml:foo:greek'},
          'game:monsters' : {'hp' : 552, 'label' : 'Queen Banshee'}}
}}}

In XMPP there are many cases where it'd be useful for generated elements to be in different namespaces like this.  A separate py:element namespace= attribute may also be useful in some situations but would increase complexity in the above examples.",enhancement,new,minor,0.9,Template processing,0.5.1,,,
