That's from IEEE 754 (a standard for floating-point arithmetic). `NaN` and -0 exist for the same reason.
Python throws an error, but numpy.divide(1., 0) will work just fine (and return inf).
I'm not sure why you're saying C throws an error. The behavior of dividing by 0 is undefined by default, but on most machines these days the hardware implements IEE-754 and the C implementation will advertise as implementing IEC 60559, so 1. / 0 will give you inf as well.