You're misunderstanding. Arch is still shipping Python 2.7 with the python2 package.
So package maintainers don't need to rewrite upstream code if it's not compatible with Python 3; they just need to update dependencies and set paths to point to the /usr/bin/python2 binary.
I imagine that someone could easily be packaging 10 Python apps or libraries. He can't be upgrading all that code to Python 3 as it is not always a trivial task and would require a lot of work and constant patching if the developing team keeps working with Python 2.X
But overall, I think this is a good way to push developers to upgrade or at least prepare more to move to Python 3.