➜

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.

classification
Title: wrong output of np.lcm.reduce(*awg)
Type: Stage: resolved
Components: Documentation Versions: Python 3.8
process
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, mark.dickinson, zlwq
Priority: normal Keywords:

Created on 2021-06-29 14:55 by zlwq, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
a text for lcm() in numpy.py zlwq, 2021-06-29 14:55
Messages (2)
msg396742 - (view) Author: 申泷轩 (zlwq) Date: 2021-06-29 14:55 
np.lcm.reduce([1,2,3,100])
Out[125]: 300

np.lcm.reduce([1,2,3,100,101])
Out[126]: 30300

np.lcm.reduce([1,2,3,100,101,99019])
Out[127]: -1294691596

30300*99019
Out[128]: 3000275700
msg396744 - (view) Author: Mark Dickinson (mark.dickinson) * (Python committer) Date: 2021-06-29 15:36 
It looks as though you're reporting an issue with NumPy; this tracker is for the Python core language, which doesn't include NumPy.

For NumPy bugs, use the NumPy bug tracker at https://github.com/numpy/numpy/issues. (Though I don't think this _is_ a NumPy bug: it's simply the result of integer overflow in NumPy.)
History
Date User Action Args
2022-04-11 14:59:47adminsetgithub: 88702
2021-06-29 15:36:52mark.dickinsonsetstatus: open -> closed

nosy: + mark.dickinson
messages: + msg396744

resolution: third party
stage: resolved
2021-06-29 14:55:23zlwqcreate