bug reporting

[Arthur Siegel]

>Yes, that is sort of what I am hoping for, when I post stuff here. I've
>gotten a lot of "submit it as a bug report" responses, more recently.
>Anyhow, the one in the thread you continued this from...I have now
>submitted it as a bug report. However, as I continue to work on this
>problem (sort of trying to see if I can fix it or at least see if I can
>understand what's causing it), I'm not so sure it will end up to be a bug
>report after all. It may end up to be a problem in my own code.  :/

I ended  up posting my issue up to the tutor list, where Danny Yoo picked
it up and did the kind of analysis I wouldn't know how to undertake.

I know you are active there - so assumedly you saw it.  Danny has helped
me before, and I was actually figuring I might get his attention to the 
problem by posting on tutor. 

He concluded:

"In any case, this is definitely a bug in the documentation.  Arthur, bring
it up on comp.lang.python and Sourceforge again.  Someone should really
look at your example, since it does seem serious... if not a little
obscure.  *grin*"

I have posted the issue up to sourceforge (but didn't get a nice
"submission received" kind of message at the end of the process -
hope it made it)

Must admit some perverse satisfaction in uncovering something
that perhaps has some significance. Bit of a Pythonic
coming of age.

And thanks, Danny.

Art