LGTM, can't see a case where this might go wrong (errors and type checks are handled before the added code).

It also seems a sufficiently common case to optimise it internally. The 2**n spelling is easier to read and to get right than the shifting, so it's good to make both similarly fast to remove an excuse for micro optimisations in Python code.