There is a lot of incoherence and inconsistencies in sage
hash functions. Two reasons that might explain the design in
some particular situation
* high hash collisions with tuple of integers in Python
(because hash(-1) is -2)
>>> hash((-1,-2)) == hash((-1,-1))
True
* speed. With your version th
I have opened https://trac.sagemath.org/ticket/32737 for this
On Thursday, October 21, 2021 at 12:43:30 AM UTC-7 Lorenz Panny wrote:
>
> This looks like a buffering issue: The test was apparently written
> under the expectation that the Python print() would get flushed to
> stdout before the GMP
This looks like a buffering issue: The test was apparently written
under the expectation that the Python print() would get flushed to
stdout before the GMP error gets printed in the library call, but
this is untrue if Python caches the output until after calling GMP.
Hence we're seeing the output
Hello,
it seems that all patchbots currently break on a doctest in integral.pyx,
see below. The cause is not identified so far. Could be random-seed usage,
changes in gmp, or anything else. Any idea ?
Frédéric
File "src/sage/rings/integer.pyx", line 6434, in
sage.rings.integer.Integer._shift_
