Yes I get the popup every time I use it. another anon monk advised to try "next" in place of break and this worked a treat i.e. we're back in business but getting the translation from break to next by reading TK's documentation as activestate suggested is at best optimistic I fear i.e. one continues a loop whereas the other drops out of a loop. That's far from intuitive to me without visibility of the additional structures involved or a well-documented lookup table e.g. for "break"...use "next" in callbacks.