Message364244
| Author | belopolsky |
|---|---|
| Recipients | Yi Luan, belopolsky, p-ganssle |
| Date | 2020-03-15.16:07:09 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1584288429.34.0.269046901792.issue39970@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
I am sure this has been reported before – I will try to find the relevant issue. This behavior is correct and documented. The only improvement that we can consider is to make it more explicit that utcnow is deprecated and the correct way to obtain the UTC timestamp is datetime.now(timezone.utc).timestamp() |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2020-03-15 16:07:09 | belopolsky | set | recipients: + belopolsky, p-ganssle, Yi Luan |
| 2020-03-15 16:07:09 | belopolsky | set | messageid: <1584288429.34.0.269046901792.issue39970@roundup.psfhosted.org> |
| 2020-03-15 16:07:09 | belopolsky | link | issue39970 messages |
| 2020-03-15 16:07:09 | belopolsky | create | |