![](https://secure.gravatar.com/avatar/59bdb3784070f0a6836aca9ee03ad817.jpg?s=120&d=mm&r=g)
On Tue, Jul 6, 2010 at 4:13 PM, Robin <robince@gmail.com> wrote:
On Tue, Jul 6, 2010 at 3:04 PM, Bruce Southey <bsouthey@gmail.com> wrote:
Windows 7 is a big improvement over Vista but both suffer the transisition from 32-bit to x64 64-bit architecture (similar to Linux when these x64 cpu's came out). Sure most people do not develop with Windows but do not equate that with a lack of interest. The problem is that Windows and how the Windows binaries are build just makes it very extremely hard to develop for.
Yes, I was really surprised at this. I don't know very much about the workings of Python, but presumably theres a reason the Python people couldn't have made ints on win64 proper 64 bit ints using whatever type microsoft requires instead of just sticking with 32bit C longs.
I am not sure why you think that's the problem to the issues you are describing. Numpy does use a type which is 64 bits for indexing on windows as everywhere else, and that's not the cause of the issues you have described so far. The random shuffle limitation for example is not windows specific, for example. Concerning sparse matrices, the index is currently limited to 32 bits: you can change this by hand if you need 64 bits indexing (in sparsetools.i, add DECLARE_INDEX_TYPE(npy_intp)). David