Message321110
| Author |
p-ganssle |
| Recipients |
Denny Weinberg, FrankBlabu, Jim.Jewett, Roman.Evstifeev, ammar2, belopolsky, christian.heimes, cschramm, josh.r, ncoghlan, ndjensen, p-ganssle, palm.kevin, steve.dower, yan12125 |
| Date |
2018年07月05日.15:53:14 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1530805994.19.0.56676864532.issue27400@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Hmm. I never noticed this. In the past I have used the (undocumented) PyDateTimeAPI struct, which the official macros wrap. I'm not sure how official that struct is considering it doesn't show up in the documentation.
I agree that it should be possible to construct TZ-aware datetimes using the official C API, so I guess the question is whether to add a bunch more macros or document the existing struct. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2018年07月05日 17:14:18 | pablogsal | unlink | issue27400 messages |
| 2018年07月05日 15:53:14 | p-ganssle | set | recipients:
+ p-ganssle, ncoghlan, belopolsky, christian.heimes, palm.kevin, Roman.Evstifeev, Jim.Jewett, steve.dower, josh.r, ndjensen, yan12125, Denny Weinberg, ammar2, cschramm, FrankBlabu |
| 2018年07月05日 15:53:14 | p-ganssle | set | messageid: <1530805994.19.0.56676864532.issue27400@psf.upfronthosting.co.za> |
| 2018年07月05日 15:53:14 | p-ganssle | link | issue27400 messages |
| 2018年07月05日 15:53:14 | p-ganssle | create |
|