Message250107
| Author | vstinner |
|---|---|
| Recipients | BreamoreBoy, aconrad, belopolsky, larry, mark.dickinson, python-dev, r.david.murray, tbarbugli, tim.peters, trcarden, vivanov, vstinner |
| Date | 2015-09-07.12:56:39 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1441630599.78.0.0669517848521.issue23517@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> All you need to do is to revert a few chunks of 1e9cc1a03365 where the regression was introduced. Hum, please don't revert this change. I spent a lot of days to write pytime.c/.h. My patches add more unit tests to datetime, to test the exact rounding mode. > Well, for now I assume it really truly genuinely isn't going in 3.5.0. I suppose we can debate about 3.4.x and 3.5.1 later, once we have a fix everybody is happy with. The rounding mode of microseconds only impact a very few people. The rounding mode changed in 3.3, again in 3.4 and again in 3.5. This issue is the first bug report. So I think it's fine to modify 3.4.x and 3.5.x. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-09-07 12:56:39 | vstinner | set | recipients: + vstinner, tim.peters, mark.dickinson, belopolsky, larry, r.david.murray, aconrad, BreamoreBoy, vivanov, python-dev, tbarbugli, trcarden |
| 2015-09-07 12:56:39 | vstinner | set | messageid: <1441630599.78.0.0669517848521.issue23517@psf.upfronthosting.co.za> |
| 2015-09-07 12:56:39 | vstinner | link | issue23517 messages |
| 2015-09-07 12:56:39 | vstinner | create | |