give a warning if we use a numpy version that have a memory leak and that we exeecute code that will hit that leak.

Some c_code regerated by the conv op was hard coding some shape info in some case. When those case are not true, their was no error generated.

fix conv op compilation when the c_code fct was changing the signature of the c code. That is not allowed.

Added ImagesFromNeighbourhoods and two basic tests... but the tests are commented out for the moment

The bug make the CudaNdarray.__getitem__ return something with the wrong number of dimensions.

The bug happen with the param of __getitem__ is a tuple with element that are a numpy.int under Ubuntu(system where PyInt_Check(numpy.int) return false.

Their is many different rounding algo. So we don't create a round fct, but one for a 2 differents version(c round fct() and numpy.round)

We do this as in some case the test was failing during theano fct call.(i.e. under ubuntu)
As we use theano.tensor.scalar and not theano.scalar.scalar normally this is not a problem.

added comment to scalar c_extract function, explaining one way to go about fixing the broken scalar module