----- Original Message -----
From: "Steven Taschuk" <(E-Mail Removed)>
To: <(E-Mail Removed)>
Sent: Saturday, June 28, 2003 9:26 AM
Subject: Re: Re/Unresolved bug?
> Quoth Xavier:
> > t:163: SyntaxWarning: name 'VERBOSE' is assigned to before global
> > declaration
> > def main():
> > (no debugging symbols found)...(no debugging symbols found)...(no
> > symbols found)...
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x0807f022 in PyErr_NormalizeException ()
> [...in 2.2.3 it dies with no segfault by no exception message either...]
> Could you post a minimal example of code which provokes this
> Without seeing code, I speculate irresponsibly: the SyntaxWarning
> is unrelated to the segfault; the segfault might be due to
> PyErr_NormalizeException somehow being called when no exception
> has been set. (The bug fix in Python/errors.c revision 2.77 (part
> of 2.3b1, backported to 2.2.3 in revision 220.127.116.11) seems
> Steven Taschuk http://www.velocityreviews.com/forums/(E-Mail Removed)
> "What I find most baffling about that song is that it was not a hit."
> -- Tony Dylan Davis (CKUA)
"Xavier" <(E-Mail Removed)> wrote in message
> Thanks for your reply. Here is the exact, waiting to be fixed code:
Suggestion: Put one "global METHOD, TARGETFILE, SINGLEIP, <etc>"
statement after "def main()" and remove all the others buried within
if blocks within a for block within an outer if block (and any past
where I read).
Reason: variables within a function are unconditionally local or
global within a particular function. They cannot be one thing here
and the other elsewhere depending on which conditional statements are
true. So the standard (and tested) place for a global statement is at
the top of the function. There is no possible advantage to your
unusual placement and the now obvious possible disadvantage that it
confuses the compiler, even if technically legal.