To me, ValueError("non-integer arg 1 for randrange()") (ValueError('bad type') is a bit painful to read.  We do sometime fix such bugs, when not documented, in future releases.

Current the doc, "Return a randomly selected element from range(start, stop, step). This is equivalent to choice(range(start, stop, step))", implies that both accept the same values, which most would expect anyway from the names.  Being selectively 'generous' in what is accepted is confusing.

For the future: both range and math.factorial raise
TypeError: 'float' object cannot be interpreted as an integer
The consistency is nice.  randrange should say the same after deprecation.