strange error whilst porting to 2.6

[Steve Holden]

Benjamin Peterson wrote:
> Robin Becker <robin <at> NOSPAMreportlab.com> writes:
>> Well that's not really acceptable as a solution is it? :)
> 
> This doesn't happen in Python 3.0,
> so you could port to that. :)
> 
> In 2.7, the better recursion depth
> handling
> in Py3k may be backported,but the
> best you can do for now is not touch
> the recursion limit or just shut
> the error up.
> 
Perhaps an interim solution would implement an error message more
helpful in ensuring the exception not be raised? This is currently a bit
like "Your code is wrong": strictly correct, and totally unhelpful.

regards
 Steve
-- 
Steve Holden        +1 571 484 6266   +1 800 494 3119
Holden Web LLC              http://www.holdenweb.com/