On Thu, Sep 8, 2016, at 16:01, Chris Barker wrote:
> Is there a "long" in there anywhere in the integer implementation?
The python 2 long type is the python 3 int type. The python 2 int type
is gone.
> I don't have py3 running on win64 anywhere right now, but in win64 py2,
> that would give you:
>
> dtype('int32')
>
> as it's a "long" under the hood
That's numpy's decision, there's nothing "built-in" about it.
> (and I'm pretty sure that is not because of numpy code itself, but rather
> how Cpython is written/compiled)
Nope.
https://github.com/numpy/numpy/blob/master/numpy/core/src/multiarray/common.c#L105
Note that PyInt_Check doesn't exist anymore in Python 3. NumPy provides
its own definition:
https://github.com/numpy/numpy/blob/master/numpy/core/include/numpy/npy_3kcompat.h#L35
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4