Message276748
I agree on reflection that a single nanoseconds integral value makes more sense. This then requires refactoring of the existing code so that existing tests continue to pass using a microsecond property.
Code using ONLY nanoseconds is a disjoint case, for which new tests will be required. It clearly cannot be expected to be backwards compatible with pre-implementation versions.
Does it make sense to define behaviour for cases where the user attempts to MIX microseconds and nanoseconds? One validation I would suggest if so is that in the presence of a microseconds specification a constraint of 0 <= nanoseconds < 1000 must be imposed. |
|
Date |
User |
Action |
Args |
2016-09-16 20:38:15 | holdenweb | set | recipients:
+ holdenweb, lemburg, tim.peters, belopolsky, vstinner, pythonhacker, Arfrever, r.david.murray, andrewclegg, Ramchandra Apte, serhiy.storchaka, goshawk, Niklas.Claesson, mdcb808@gmail.com, scoobydoo, tomikyos |
2016-09-16 20:38:14 | holdenweb | set | messageid: <1474058294.81.0.704335473154.issue15443@psf.upfronthosting.co.za> |
2016-09-16 20:38:14 | holdenweb | link | issue15443 messages |
2016-09-16 20:38:14 | holdenweb | create | |
|