Gregory P. Smith <g...@krypto.org> added the comment: In your back traces notice that the size= argument is clearly nonsensical.
Regardless, i can't reproduce this on any of my systems (I don't have a suse system of any sort). If that is the only place you are seeing this I strongly suspect you've got something going on there. Without some way to reproduce this or more detailed debugging info (point to the line of python that dies and single step into the C code in gdb from there printing out relevant state along teh way to see what happens) there is nothing I can do. ---------- resolution: -> works for me status: open -> closed title: Test fail for sha512 -> Test fail for sha512 - _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8073> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
