On Thu, Sep 8, 2016, at 12:30, Chris Barker wrote: > That's why I said "based on" -- under the hood, a C type is used, and > IIUC, that type has been "long" for ages. And a long on Windows 64 > (with the MS compiler anyway) is 32 bit, and a long on *nix (with the > gnu compilers, at least) is 64 bits. > > This doesn't expose itself to pure python (and sys.maxint is now gone) > but it does get exposed in the C API, and in particular, when passing > data back and forth between numpy and pure python (numpy doesn't > support an unlimited integer like python), or working with buffers or > bytearrays, or whatever in Cython.
I'm not sure "the builtin integer type" was the right term for what you're referring to. You're talking about changing Py_ssize_t, right? _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
