This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients mark.dickinson
Date 2018-07-02.13:43:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1530539031.68.0.56676864532.issue34023@psf.upfronthosting.co.za>
In-reply-to
Content
On Python 2.x on Windows, creating a timedelta with an `np.int32` instance for the number of seconds can (somewhat) silently give wrong results.

Enthought Deployment Manager -- https://www.enthought.com
Python 2.7.13 |Enthought, Inc. (x86_64)| (default, Mar  2 2017, 16:05:12) [MSC v.1500 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy as np
>>> import datetime
>>> datetime.timedelta(seconds=np.int32(123456789))
__main__:1: RuntimeWarning: overflow encountered in long_scalars
datetime.timedelta(-1, 84354, 76480)

There's at least a warning from NumPy there as NumPy attempts to scale the np.int32 by 10**6, but depending on settings and on how the code is invoked, the user may not see that warning.

This is not an issue on Python 3.x / Windows or on Python 2.x / Unix; in both those cases, the same code gives a TypeError.

This is related to, but not the same as, #5476.

This may well count as a "won't fix", but it seemed at least worth reporting.
History
Date User Action Args
2018-07-02 13:43:51mark.dickinsonsetrecipients: + mark.dickinson
2018-07-02 13:43:51mark.dickinsonsetmessageid: <1530539031.68.0.56676864532.issue34023@psf.upfronthosting.co.za>
2018-07-02 13:43:51mark.dickinsonlinkissue34023 messages
2018-07-02 13:43:51mark.dickinsoncreate