Unless you need a library that's only available in 2, I'd use 3 at this point. But virtualenv takes the pain away from having to choose, since you can just create a new "environment" with 2 or 3 depending upon your needs for a project.

If you're coming from the Ruby scene, think of virtualenv as Python's take on RVM.