[issue24605] segmentation fault at asciilib_split_char.lto_priv

josch added the comment: I do not see any module implemented in C in the imports. Is there a way to find out from where the segmentation fault came? -- ___ Python tracker <http://bugs.python.org/issue24

[issue24605] segmentation fault at asciilib_split_char.lto_priv

New submission from josch: Hi, sometimes (but not reliably reproducibly, one has to run it a few times) I get a segmentation fault when running the following networkx based Python code on large input graphs: https://gitlab.mister-muffin.de/debian-bootstrap/botch/blob/master/tools/graph

[issue22621] Please make it possible to make the output of hash() equal between 32 and 64 bit architectures

josch added the comment: Thank you for your quick reply. Yes, as I wrote above there are ways around it by creating a stable in-memory representation and comparing that to a stable in-memory representation of the expected output. Since both input are several hundred megabytes in size, this

[issue22621] Please make it possible to make the output of hash() equal between 32 and 64 bit architectures

New submission from josch: I recently realized that the output of the following is different between 32 bit and 64 bit architectures: PYTHONHASHSEED=0 python3 -c 'print(hash("a"))' In my case, I'm running some test cases which involve calling a Python module whic