maybe a fakeable traceback is a good idea nonetheless? (we can provide it directly from some __pypy__ module instead of a general mechanism)
On Fri, Jul 4, 2014 at 5:02 PM, Antonio Cuni <[email protected]> wrote: > Hi Armin, > > >> >> As you have noticed, this is an old feature not supported any more >> since a long time (and mostly untested). It was an experimental >> feature that turned out not to be useful in practice. Just using >> regular Python, you can mostly achieve the same effects, with the >> exception (mostly) of pretending to have an object of some built-in >> type for built-in function calls. > > > actually, jinja2 uses transparent proxy to create fictiious traceback > chains: > https://github.com/mitsuhiko/jinja2/blob/master/jinja2/debug.py > > if we decided that transparent proxies are not supported or deprecated, we > should remove them and tell people to stop using them. > > > _______________________________________________ > pypy-dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/pypy-dev > _______________________________________________ pypy-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-dev
