Python 2.0.1 "re.match" enters infinite loop for
a regular expression that was carefully designed not
to lead to loops (an easy expression).

See attached file.

Logged In: YES 
user_id=31435

Assigned to /F, but I don't see a bug here.  While your 
regexp should be speedy *when* applied to a string that 
actually matches (the regexp does not match the long string 
in your test case), you create an exponential number of 
backtracking possibilities by repeating \s* at both ends of 
the first repeated group (in effect, you're specifying an 
unbounded number of instances of the highly ambiguous 
\s*\s*).  So when the regexp doesn't match, it can be 
unboundedly slow.  This minor rewrite doesn't have that 
problem (it simply moves the first \s* "out of the loop"):

r='</[^>]*>\s*(<[?][^>]*>\s*)+<[^/?][^>]*>'

BTW, your test string doesn't match because it ends with

</list>

It *would* match if it ended with

<list>

It's unclear whether you expected it to match.

Logged In: YES 
user_id=6380

A general comment for folks who report problems with regular
expressions: Komodo has a tool that debugs a regular
expression, by stepping through its execution step by step.
Very educational, and would probably help understanding
what's going on in cases like the case here reported.

Logged In: YES 
user_id=38376

See Tim's analysis for the correct solution.

(time to add a "canned response"?)

Logged In: YES 
user_id=265829

Thank you all!

I learned something...