[Python-Dev] PEP 410 (Decimal timestamp): the implementation is ready for a review (original) (raw)
Georg Brandl g.brandl at gmx.net
Fri Feb 17 19:00:16 CET 2012
- Previous message: [Python-Dev] PEP 410 (Decimal timestamp): the implementation is ready for a review
- Next message: [Python-Dev] PEP 410 (Decimal timestamp): the implementation is ready for a review
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 17.02.2012 10:28, schrieb Steven D'Aprano:
Georg Brandl wrote:
Am 16.02.2012 11:14, schrieb "Martin v. Löwis":
Am 16.02.2012 10:51, schrieb Victor Stinner:
2012/2/16 "Martin v. Löwis" <martin at v.loewis.de>:
Maybe an alternative PEP could be written that supports the filesystem copying use case only, using some specialized ns APIs? I really think that all you need is st{a,c,m}timens fields and os.utimens(). I'm -1 on that, because it will make people write complicated code. Python 3.3 has already APIs for nanosecond timestamps: os.utimensat(), os.futimens(), signal.sigtimedwait(), etc. These functions expect a (seconds: int, nanoseconds: int) tuple. I'm -1 on adding these APIs, also. Since Python 3.3 is not released yet, it's not too late to revert them. +1. Sorry, is that +1 on the revert, or +1 on the APIs?
It's on what Martin said; you're right, it was a bit too ambiguous even for a RM :)
Georg
- Previous message: [Python-Dev] PEP 410 (Decimal timestamp): the implementation is ready for a review
- Next message: [Python-Dev] PEP 410 (Decimal timestamp): the implementation is ready for a review
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]