This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author orsenthil
Recipients ajaksu2, ak, jjlee, orsenthil, shashank
Date 2009-11-22.15:33:57
SpamBayes Score 0.00034427148
Marked as misclassified No
Message-id <1258904039.64.0.242374175705.issue5007@psf.upfronthosting.co.za>
In-reply-to
Content
This bug is not reproducible in trunk, py3k and is not reproducible in
py26 releases too. I tried to hunt down if any changes in the code-line
from py2.5 to py2.6 had effect on the behavior mention (BadStatusLine) ,
but don't see any. 

I am closing this as works for me.
History
Date User Action Args
2009-11-22 15:34:00orsenthilsetrecipients: + orsenthil, jjlee, ajaksu2, ak, shashank
2009-11-22 15:33:59orsenthilsetmessageid: <1258904039.64.0.242374175705.issue5007@psf.upfronthosting.co.za>
2009-11-22 15:33:58orsenthillinkissue5007 messages
2009-11-22 15:33:57orsenthilcreate