Message338054
| Author | ncoghlan |
|---|---|
| Recipients | Yasser Alshalaan, belopolsky, docs@python, fdrake, miss-islington, ncoghlan, p-ganssle |
| Date | 2019-03-16.05:34:11 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1552714452.17.0.780686096074.issue36138@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
I've merged Yasser's PR (thank you!), but in the review discussion for that, we noticed something else: the `total_seconds()` documentation mentions the floating point dynamic resolution problem, but doesn't mention using `//` or `divmod()` as the fix for that, while the operator table doesn't mention the dynamic resolution problem at all. So I haven't closed the issue yet, as fixing that feel in-scope for this issue, even though I didn't want to hold up the initial PR for it. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-03-16 05:34:12 | ncoghlan | set | recipients: + ncoghlan, fdrake, belopolsky, docs@python, p-ganssle, miss-islington, Yasser Alshalaan |
| 2019-03-16 05:34:12 | ncoghlan | set | messageid: <1552714452.17.0.780686096074.issue36138@roundup.psfhosted.org> |
| 2019-03-16 05:34:12 | ncoghlan | link | issue36138 messages |
| 2019-03-16 05:34:12 | ncoghlan | create | |