No, this has been a source of subtle confusion.  We have the big warning at the top that the API "may change", so I think that's ok to just make it always units now.

You might want to change it to ``2-tuple`` though, just so its completely clear.

I think it's ok if `__init__` gets the units for the bounds from the input units though - I *think* that was effectively what was happening before.  E.g. ``Angle(1,'hr', bounds=(0,12))`` means the upper bound goes to 12 hrs, without need to explicitly specify the unit of the bounds separately.  But ``Angle(1,'hr', bounds=(0,Angle(180,'deg')))`` should also work (maybe this is true already, I didn't check).