delta/python-packages/numpy.git/numpy/core/src/scalarmathmodule.c.src, branch v1.9.2 github.com: numpy/numpy.git ENH: add scalarmathmodule.h.src with integer overflow functions 2013-10-14T22:37:50+00:00 Julian Taylor jtaylor.debian@googlemail.com 2013-10-14T19:55:33+00:00 3f5ef54558e3546134be32edfdc2ed510a9cc6ca and use them in scalarmathmodule.c instead of the old (disabled) ones. 
and use them in scalarmathmodule.c instead of the old (disabled) ones.
Revert "Merge pull request #3567 from arinkverma/avoid_conversion" 2013-09-03T12:41:28+00:00 Charles Harris charlesr.harris@gmail.com 2013-09-03T12:41:28+00:00 b35728d7858a4c4d46eefd936c33a0ffa6593082 This reverts commit de9f1c92d3ca0920bce915438f0406f587aa98db, reversing changes made to d958dec676beeac218a118fac084fa8b14bc9171. There is a change of behavior in conversion of signed to unsigned PyLong that shows up on my machine. For some reason this did not show up in the travisbot tests. This reverts the merge that led to this problem until it can be sorted out. Error shows up as numpy/core/arrayprint.py", line 653, in __call__ if _MININT < x < _MAXINT: OverflowError: can't convert negative int to unsigned 
This reverts commit de9f1c92d3ca0920bce915438f0406f587aa98db, reversing
changes made to d958dec676beeac218a118fac084fa8b14bc9171.

There is a change of behavior in conversion of signed to unsigned
PyLong that shows up on my machine. For some reason this did not show
up in the travisbot tests. This reverts the merge that led to this
problem until it can be sorted out. Error shows up as

numpy/core/arrayprint.py",
line 653, in __call__
    if _MININT < x < _MAXINT:
OverflowError: can't convert negative int to unsigned
Check for error value by PyLong_AsUnsignedLong as (unsigned long)-1 2013-08-30T21:29:35+00:00 Arink Verma arinkverma@gmail.com 2013-08-30T21:29:35+00:00 7ed2c9bfdcd2eded4c42ec485cce8e6e3a69308c 






Replaced PyInt_As_Long with PyInt_AsLong and  errorchecking
2013-08-29T20:44:29+00:00

Arink Verma
arinkverma@gmail.com

2013-08-29T20:34:52+00:00

d334dbd400964515bb392f3f9d7978d0ddb2a9a6












Added PyInt_CheckExact for python < 3 and error check for PyLong_AsLong
2013-08-29T20:44:29+00:00

Arink Verma
arinkverma@gmail.com

2013-08-27T16:35:38+00:00

7b415b26f4a1d58164a69ef44fb501fbd93e666f












Extracting longlong value without converting it to NyType
2013-08-29T20:44:29+00:00

Arink Verma
arinkverma@gmail.com

2013-08-03T12:39:55+00:00

79342d5993168a5e43d57924bb3fa75a4fa3ec01












ENH: Avoiding conversion of integer to NumPy Scalar.
2013-08-29T20:44:29+00:00

Arink Verma
arinkverma@gmail.com

2013-08-02T22:55:46+00:00

70de8aa2b3a3b300c6a858cbdbb9226ce46591e1

There is a bottleneck in scalar operations, when trying to extract the
underlying C value from a Python integer/float. I have avoid conversion
for know integer type but extracting its value.





There is a bottleneck in scalar operations, when trying to extract the
underlying C value from a Python integer/float. I have avoid conversion
for know integer type but extracting its value.







STY: Giant whitespace cleanup.
2013-08-18T17:20:45+00:00

Charles Harris
charlesr.harris@gmail.com

2013-08-18T17:16:06+00:00

8ddb0ce0acafe75d78df528b4d2540dfbf4b364d

Now is as good a time as any with open PR's at a low.





Now is as good a time as any with open PR's at a low.







Merge pull request #2941 from raulcota/avoid_create-kill_npscalars
2013-07-29T17:35:43+00:00

Charles Harris
charlesr.harris@gmail.com

2013-07-29T17:35:43+00:00

32206dd79cafdce87cfb0db91903084c2fe2e473

Avoid conversion to NumPy Scalar




Avoid conversion to NumPy Scalar






MAINT: Remove outdated version checks.
2013-07-11T18:43:18+00:00

Charles Harris
charlesr.harris@gmail.com

2013-07-11T18:08:49+00:00

28eadc0e31ca7aea5c679023d1e703856f45c879

Because Numpy 1.8.0 will no longer supports Python versions < 2.6 we
no longer need to check for that and can also remove the code that is
specific to those earlier versions.

To make this a bit safer, the toplevel setup.py file now contains a
check of the Python version number and raises an error when run by an
unsupported version.





Because Numpy 1.8.0 will no longer supports Python versions < 2.6 we
no longer need to check for that and can also remove the code that is
specific to those earlier versions.

To make this a bit safer, the toplevel setup.py file now contains a
check of the Python version number and raises an error when run by an
unsupported version.