This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author arhadthedev
Recipients arhadthedev, gvanrossum, hroncok, mark.dickinson, remi.lapeyre, serhiy.storchaka, vstinner
Date 2021-12-09.07:32:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639035128.8.0.138839423689.issue36048@roundup.psfhosted.org>
In-reply-to
Content
The reporter gave more details (<https://github.com/python/cpython/pull/11952#issuecomment-989430968>):

> Literally this is ok in C++ with Qt:
>
>     float x = 2.3, y = 1.1;
>     auto p = QPoint(x, y); // QPoint only takes 2 int params.. this works in C++; floats can be always be implicitly converted to int
>
> Same code, more or less, in Python3.10 is now broken:
>
>     x = 2.3
>     y = 1.1
>     p = QPoint(x, y)  # This fails, where previously it worked on every Python version since the age of the dinosaurs...
>
> Note that most of the API for PyQt5 is auto-generated from the function signatures of the C++. So in this case QPoint takes 2 ints for its c'tor (just like in C++).. and breaks on Python 3.10 if given floats, when previously it worked just fine with either ints or floats. This is just 1 example. But many codebases that use PyQt5 are hit by breakages like this one now.
History
Date User Action Args
2021-12-09 07:32:08arhadthedevsetrecipients: + arhadthedev, gvanrossum, mark.dickinson, vstinner, serhiy.storchaka, hroncok, remi.lapeyre
2021-12-09 07:32:08arhadthedevsetmessageid: <1639035128.8.0.138839423689.issue36048@roundup.psfhosted.org>
2021-12-09 07:32:08arhadthedevlinkissue36048 messages
2021-12-09 07:32:08arhadthedevcreate