On Wed, 6 Jun 2001 richard@bizarsoftware.com.au wrote: > ... at least then we know what the exception is. : > Again - try that code in an interactive interpreter if you really want to > find out what's going on... Yeah, thanks, that would work as a workaround, but isn't this buggish behaviour?