--HG--
extra : transplant_source : 4%93%F3HQ/%0C%D4%28%FB23%1E%F6%FE%E1%D8%8AT%EB

replace plain '#define CYTHON_PEP393_ENABLED' by flag #define as 1 or 0 to make it usable from Cython code

--HG--
extra : transplant_source : %98%A3s%16%85%D7%5C%18%AC%C4%EFe%A624ZcU%EC%A8

--HG--
extra : transplant_source : %9A%B9%B3%3B%3E%07%C1%F5H%3F%AFm%F1t%B9%3Cg4%C9/

--HG--
extra : rebase_source : ea120f4d95e0ea2ee49fa91c6bb2e0534fc53730

--HG--
extra : rebase_source : 255f3e4df8a66d204b2390ea5e566aa758839b94

work around reversed(range()) bug by disabling optimised looping for non-trivial step values (ticket #763)

Add "nogil" to the stdc++ pxd files

NumPy is starting to seriously deprecating access to the member fields
in an ndarray (it was always frowned upon, but now it is starting to
become enforced). To support the large body of Cython code out there
accessing these fields (arr.shape[0] and so on), we special-case
PyArrayObject in Cython, with special knowledge of the NumPy API.

Ideally, we may introduce features in Cython in the future that allows
specifying this kind of magic with syntax in pxd files, and then we can
move away from special-casing NumPy.