mechanism for saving and using pre-built venv from s3 on jenkins

Does this need to take place in a separate venv? How can we ensure what's being built will not contain older versions of libs? (E.g., whatever is running paver must have had some stuff in it...)