Message106496
I have no opinion on the first question. I would be fine with a simple "soft" deprecation where we simply add a note in documentation warning that these methods create naive datetime instances and it is preferable to use aware variants produced by meth(utc). On the other hand eventually removing these methods will make maintenance easier. Sorry I cannot offer more help with this decision.
With respect to the second question, I would be against mixed C/Python implementation. I would also like to see C API to the new concrete tzinfo classes. |
|
Date |
User |
Action |
Args |
2010-05-26 00:39:24 | belopolsky | set | recipients:
+ belopolsky, doerwalter, brett.cannon, ggenellina, pitrou, vstinner, ajaksu2, kawai, eric.araujo, rafe |
2010-05-26 00:39:24 | belopolsky | set | messageid: <1274834364.0.0.183741444861.issue5094@psf.upfronthosting.co.za> |
2010-05-26 00:39:22 | belopolsky | link | issue5094 messages |
2010-05-26 00:39:21 | belopolsky | create | |
|