On 10/16/2009 3:40 PM, Tim Chase wrote: > What's always wrong is giving me an *error* when the semantics are > perfectly valid. Exactly. Which is why I expected this to be fixed in Python 3. Alan Isaac