Closed hroncok closed 2 years ago
I'm trying to figure out what exactly changed in Python. But I guess using random.randint(0, int(1e6))
would be more explicit anyway.
https://bugs.python.org/issue42222 https://github.com/python/cpython/commit/5afa0a411243210a30526c7459a0ccff5cb88494
randrange: Remove deprecated support for non-integer values
Thank you for chasing the bug!
I guess I'll replace it with 1_000_000 in that case, might be clearer anyhow.
The randint/randrange change in Python violates Python's own policy for incompatible changes. I've asked the maintainer to revert it: https://bugs.python.org/issue46624
Nevertheless, using 1_000_000 is indeed better.
Thanks!
Hello @WoLpH.
We are building all Fedora packages with Python 3.11 pre-releases to figure out all the incompatibilities early in the development cycle of the new Python version. With numpy-stl 2.16.3 and Python 3.11.0a4, we see the following errors:
I do not know yet what change in Python caused this.
And I was not able to reproduce this outside of Fedora with plain
tox -e py311
because released Cython is currently not compatible with 3.11.0a4, so NumPy installation fails.However the
random.randint(0, 1e6)
call in isolation gets it: