Le jeu. 31 oct. 2019 à 11:41, Serhiy Storchaka <storch...@gmail.com> a écrit : > I propose to deprecate the falling back to __trunc__ for converting to > int and remove it in future.
As Nick already said, I'm working on PEP 608 "Coordinated Python release" which discuss such change: https://www.python.org/dev/peps/pep-0608/ It's discussed at: https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539 Do you have an idea of how many projects would emit such warning? More and more projects are running their test suite using -Werror. Any new warning can make a project test suite to fail. I'm looking for help to build a tool to test popular PyPI projects on a modified Python version, to be able to answer to such questions. My current experimental project can only test numpy, coverage and jinja2, and it doesn't work well (especially on Python 3.9): https://github.com/vstinner/pythonci/ Since this tool doesn't exist yet and since we cannot test all PyPI projects, I suggest to keep the option of reverting such change if we consider that it breaks too many projects during the Python 3.9 beta phase. Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/KAIJFQW6OVMRYUIHL7H4KRGF2E2S6WTM/ Code of Conduct: http://python.org/psf/codeofconduct/
