Re: Hooking Mechanism when Entering and Leaving a Try Block

Date	2015-08-13 08:28 +0200
From	"Sven R. Kunze" <srkunze@mail.de>
Subject	Re: Hooking Mechanism when Entering and Leaving a Try Block
References	<55CA6D7F.1060705@mail.de> <CALwzidkBoDo1TZj2CWfimYtagtArN9r9dvw1Ke9HqcthdipV4Q@mail.gmail.com> <55CB6EAC.5040004@mail.de> <CAPTjJmoqg9sA-QB3RoRPQFx1osOYyBzff-UX8f2zrzxWpt7sYQ@mail.gmail.com> <55CB9425.5050109@mail.de>
Newsgroups	comp.lang.python
Message-ID	<mailman.159.1439447284.3627.python-list@python.org> (permalink)

Show all headers | View raw

On 12.08.2015 20:44, Sven R. Kunze wrote:
> On 12.08.2015 18:11, Chris Angelico wrote:
>> Sounds to me like you want some sort of AST transform, possibly in an
>> import hook. Check out something like MacroPy for an idea of how
>> powerful this sort of thing can be.
>
> Sounds like I MacroPy would enable me to basically insert a function 
> call before and after each try: block at import time. Is that correct 
> so far? That sounds not so bad at all.
>
>
> However, if that only works due to importing it is not a solution. I 
> need to make sure I catch all try: blocks, the current stack is in 
> (and is about to step into).
>
> Ah yes, and it should work with Python 3 as well. 

Back to topic, please. :)

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Hooking Mechanism when Entering and Leaving a Try Block "Sven R. Kunze" <srkunze@mail.de> - 2015-08-13 08:28 +0200

csiph-web