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 mark.dickinson
Recipients josh.r, mamrhein, mark.dickinson, rhettinger, serhiy.storchaka
Date 2021-08-22.09:03:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1629622983.35.0.812019170704.issue44547@roundup.psfhosted.org>
In-reply-to
Content
I think there's no reason not to keep __trunc__ and math.trunc - they're natural counterparts to floor and ceil, and there's probably at least some code out there already using math.trunc.

It's the involvement of __trunc__ in the int() builtin that I'd quite like to deprecate and eventually remove. I think at this point it complicates the object model for no particularly good reason. But this is getting off-topic for this issue; I'll open a new one.
History
Date User Action Args
2021-08-22 09:03:03mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, mamrhein, serhiy.storchaka, josh.r
2021-08-22 09:03:03mark.dickinsonsetmessageid: <1629622983.35.0.812019170704.issue44547@roundup.psfhosted.org>
2021-08-22 09:03:03mark.dickinsonlinkissue44547 messages
2021-08-22 09:03:03mark.dickinsoncreate