[issue35004] Odd behavior when using datetime.timedelta under cProfile

Batuhan added the comment: This bug is fixed in both 3.8 and 3.7, @p-ganssle what do you think about closing this? -- nosy: +BTaskaya ___ Python tracker ___

[issue35004] Odd behavior when using datetime.timedelta under cProfile

Change by Paul Ganssle : -- nosy: +p-ganssle ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35004] Odd behavior when using datetime.timedelta under cProfile

Karthikeyan Singaravelan added the comment: Thanks Anthony for the details. This was fixed in master and back ported to 3.7. The fix is also released with 3.7.1 [0] which I have verified locally. So I propose closing this issue since upgrading to the latest maintenance release fixes this.

[issue35004] Odd behavior when using datetime.timedelta under cProfile

Anthony Sottile added the comment: Here's a simpler reproduction without involving a third party library: >>> import cProfile >>> from datetime import timedelta >>> pr = cProfile.Profile() >>> timedelta.total_seconds(-25200) Traceback (most recent call last): File "", line 1, in TypeError:

[issue35004] Odd behavior when using datetime.timedelta under cProfile

New submission from Beau Gunderson : In chasing down a bug in my code that only manifests itself when running under cProfile I managed to find the culprit in datetime.timedelta by way of dateutil. Here is a small repro: https://gist.github.com/beaugunderson/68ea6424a4fdcf763ccad08e42a74974