Miro Hrončok <m...@hroncok.cz> added the comment: > Does it mean that rust-cpython was broken in Python 3.10 even if a change was > prepared with a deprecation period if Python 3.9? Does it mean that the > deprecation period was inefficient on this project?
I don't see any deprecation warning when running the test suite with Python 3.9 and I am unsure what exactly changed there. My assumption is that it might be related to PyNumber_Long not taking floats any more and I am unsure that this particular thing omitted deprecation warnings. Still investigating. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44418> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
