Matthias Klose added the comment: > I believe the unaligned memory access configure check is supposed to > prevent siphash from being used, so we might look into why that's not > working. > > IMO, though, we should just require alignment for the argument to > _PyHash_Bytes. It's private after all.
If I understand it correctly, the hash value differs depending on the kernel configuration when the python binary is built, leading to different pickle objects which cannot be shared, making them incompatible . I think the safest thing would be to remove the hash make the selection of the hash method unconditional, and to make this hash function working for all cases. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28055> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
