Senthil Kumaran <orsent...@gmail.com> added the comment: 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. ---------- resolution: -> works for me status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5007> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
