This library is a couple years old already (version 0.1.6 hit PyPi in Nov 2012). A rename at this point seems unlikely. Unlike datetime.now() and datetime.utc

This library is a couple years old already (version 0.1.6 hit PyPi in Nov 2012). A rename at this point seems unlikely. Unlike datetime.now() and datetime.utcnow(), arrow.now() produces a datetime that includes tzinfo. As long as that's on there and correct, I think the risk you describe is low.