jimbaker

3 ms·

1. 1.▲
   by jimbaker 2y ago

   Walking the call stack implies using dynamic scope, which has hard edges, vs lexical scope. See my answer earlier in this thread https://news.ycombinator.com/item?id=41272285 It's been nearly 23 years, but Python 2.2 f
2. 2.▲
   by jimbaker 2y ago

   Thanks to the feedback in the Discourse thread, we will be changing the signature such that a tag function will be passed an object implementing a Template protocol, with attributes source, for the original source string as written; and att
3. 3.▲
   by jimbaker 2y ago

   The intent here is to support the following approach for tag function authors: 1. Parse to an AST, generally using an off-the-shelf parser. In practice, it's possible to rewrite interpolations with a placeholder suitable for a given la
4. 4.▲
   by jimbaker 2y ago

   Frame hacks with sys._getframe necessarily imply dynamic scope not lexical scope. Dynamic scope does not work with nested functions, including comprehensions. See this issue with the htm library, https://github.com/jviide&#x
5. 5.▲
   by jimbaker 10y ago

   Yes, that would be true on all counts :) as one of those Jython maintainers. Jython 2.7.1 is currently bottlenecked on finalizing support on Windows for pip/setuptools. It should be the last fix.