ENH: Added test cases to ensure the behavior of integer as it is.
There is a need to add test case which ensure and maintain the behaviour
of integer. As per pr #3567, which speed up integer scalar's operations
by avoiding the conversion of integer to NumPy Scalar.
Added test case for size of long based of os
ENH: add PyDataMem_NEW_ZEROED which allocates memory with calloc
ENH: use PyDataMem_NEW_ZEROED for PyArray_Zeros

PyDataMem_NEW_ZEROED uses calloc which will take advantage of the fact
that most operating systems provide already zero initialized memory
blocks on larger allocations.
Additionally this memory can be sparse (= mapped to a single zero page)
on some systems (e.g. linux) reducing memory usage of applications
using sparse arrays.
Merge pull request #3590 from juliantaylor/calloc

    use PyDataMem_NEW_ZERO (calloc) for PyArray_Zeros
DOC: Update 1.8.0 release notes.

Add remarks on changes due in the next release and FutureWarnings.
Add notes on the new functions in the array C-API.
Add notes on the new function in th ufunc C-API.
Merge pull request #3624 from charris/update-1.8-release-notes

DOC: Update 1.8.0 release notes.
BUG: MapIter leaked itself and arr and index objects

MapIterBind incorrectly behaved when failing, cleaning up most
but not everything. The callers have to decref the mapiter
object. Which basically means that MapIterBind does not even
have to decref the new fields (they are decrefed in the
mapiter dealloc anyway).

Note that trying to add tests checking the refcounting
failed, but the tests seem to fail at least in many cases
not because of the indexing.

Closes gh-3589
Proof-of-concept for ufunc fancy indexing

Conflicts:

	numpy/core/code_generators/numpy_api.py
Add support for both unary and binary ufuncs
Add comments
Change 'select' method name to 'at'
Add unit tests

Conflicts:

	numpy/core/tests/test_ufunc.py
Check for sucessful call to MapIterBind
Misc fixes

- Fix crash when bind for second map iter fails
- Accept array like object for second operand
- Fix memory leaks
Rework 'at' method to fit customer's expectations.

'at' method should be functionally equivalent to op1[idx] += op2 (for add ufunc).
Update/expand unit tests
Update documentation for 'at' method
Add comment to 'at' method unit test
Only allow explicit index slicing in 'at' method