Hi Ben and John,
The doc page is wrong. There was suspicions of this recently with
nextafter(), but no one knew when it was introduced in numpy. Now we know
and I will update the page accordingly.
I ran into the same problem recently and discovered that nextafter() was introduced in numpy 1.4.0.