Message400064
> This decouples int from __trunc__ and leaves __trunc__ as simply the support for the math.trunc function.
Argh; copy and paste fail - I left out the crucial line.
I propose deprecating the delegation of int to __trunc__: calls to int(a) where type(a) implements __trunc__ but not __int__ or __index__ would raise a DeprecationWarning, and at some point in the future int(a) would become a TypeError. |
|
Date |
User |
Action |
Args |
2021-08-22 09:19:56 | mark.dickinson | set | recipients:
+ mark.dickinson |
2021-08-22 09:19:56 | mark.dickinson | set | messageid: <1629623996.0.0.851280826681.issue44977@roundup.psfhosted.org> |
2021-08-22 09:19:55 | mark.dickinson | link | issue44977 messages |
2021-08-22 09:19:55 | mark.dickinson | create | |
|