Author vstinner
Recipients Alexander.Belopolsky, Arfrever, belopolsky, ericography, jcea, khenriksson, larry, lars.gustaebel, loewis, mark.dickinson, nadeem.vawda, r.david.murray, rhettinger, rosslagerwall, skrah, vstinner
Date 2012-01-30.14:38:25
SpamBayes Score 5.86821e-09
Marked as misclassified No
Message-id <CAMpsgwa=r3aUDXWU=eXThftr6kJ21U0YFH_8mPARs8AS2YFvEg@mail.gmail.com>
In-reply-to <1327933258.01.0.0057281920586.issue11457@psf.upfronthosting.co.za>
Content
> (secs, nsecs) tuples are more practical in performance-critical applications
> (e.g. synchronization of timestamps between 2 trees with large number of files).

This is also why I propose an argument to choose the format: everyone
has a different use case and use cases are incompatible. Tuples are
quick to create but has not a practical API, datetime has a nice API
but also issues listed before by Martin (and don't support nanosecond
resolution currently), Decimal has a nice API but is expensive to
create, etc.
History
Date User Action Args
2012-01-30 14:38:26vstinnersetrecipients: + vstinner, loewis, rhettinger, jcea, mark.dickinson, belopolsky, lars.gustaebel, larry, nadeem.vawda, Arfrever, r.david.murray, skrah, Alexander.Belopolsky, rosslagerwall, khenriksson, ericography
2012-01-30 14:38:25vstinnerlinkissue11457 messages
2012-01-30 14:38:25vstinnercreate