<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Mar 21, 2013, at 7:17 AM, Kevin Horn <<a href="mailto:kevin.horn@gmail.com">kevin.horn@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">Notice that the node trees look exactly the same. Now this is not quite true, as there's probably some attributes on the actual Python nodes that might be used to distinguish them when writing output which aren't displayed here...they certainly get rendered into HTML differently. But the point is that the directive itself is GONE and you have no real way of recreating it from the node tree.</span></blockquote></div><br><div>The directive isn't "gone"; it turns into the attributes on the Python nodes that you're talking about. Presumably that's what's used to render it into HTML. I believe it was Doug Hellmann who indicated to Jean-Paul that this was possible.</div><div><br></div><div>Perhaps you mean "there's no public API for constructing the node tree representation of an arbitrary directive"?</div><div><br></div><div>-glyph</div></body></html>