Message336772
| Author | serhiy.storchaka |
|---|---|
| Recipients | SilentGhost, Steven Davidson, anglister, belopolsky, lemburg, p-ganssle, serhiy.storchaka, skrah, vstinner |
| Date | 2019-02-27.17:11:22 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1551287482.55.0.00821871190707.issue23607@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
No, the bug is not fixed, and this is not easy issue. You should use non-integer Decimals to reproduce it. In 3.8 this emits a deprecation warning: >>> import datetime >>> from decimal import Decimal as D >>> datetime.datetime.utcfromtimestamp(D(1425808327.307651)) <stdin>:1: DeprecationWarning: an integer is required (got type decimal.Decimal). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. datetime.datetime(2015, 3, 8, 9, 52, 7) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-02-27 17:11:22 | serhiy.storchaka | set | recipients: + serhiy.storchaka, lemburg, belopolsky, vstinner, SilentGhost, skrah, p-ganssle, anglister, Steven Davidson |
| 2019-02-27 17:11:22 | serhiy.storchaka | set | messageid: <1551287482.55.0.00821871190707.issue23607@roundup.psfhosted.org> |
| 2019-02-27 17:11:22 | serhiy.storchaka | link | issue23607 messages |
| 2019-02-27 17:11:22 | serhiy.storchaka | create | |