Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #95335 > unrolled thread

Re: Hooking Mechanism when Entering and Leaving a Try Block

Started by"Sven R. Kunze" <srkunze@mail.de>
First post2015-08-13 08:28 +0200
Last post2015-08-13 08:28 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

#95335 — Re: Hooking Mechanism when Entering and Leaving a Try Block

From"Sven R. Kunze" <srkunze@mail.de>
Date2015-08-13 08:28 +0200
SubjectRe: Hooking Mechanism when Entering and Leaving a Try Block
Message-ID<mailman.159.1439447284.3627.python-list@python.org>
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. :)

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web