That has nothing to do with pyenv.

Also, this really isn't a problem -- just blast out of the old venv, make a new one with a new version, and you're good.