pyv rc not use the current python distribution

[kyp76]

set to reproduce

>> pyv l 
# distributions
 from_path:Python 3.6.8:/home/cloud-user/local/pyv/venvs/spintest/bin
 Python-3.6.5:Python 3.6.5:/home/cloud-user/local/pyv/distributions/Python-3.6.5
*Python-3.6.8:Python 3.6.8:/home/cloud-user/local/pyv/distributions/Python-3.6.8

# virtualenvs
 ansible:Python 3.6.8:/home/cloud-user/local/pyv/venvs/ansible
 hermes:Python 3.6.8:/home/cloud-user/local/pyv/venvs/hermes
 iamaas:Python 3.6.8:/home/cloud-user/local/pyv/venvs/iamaas
 sg_hermes:Python 3.6.8:/home/cloud-user/local/pyv/venvs/sg_hermes
*spintest:Python 3.6.8:/home/cloud-user/local/pyv/venvs/spintest

pyhton dist = Python-3.6.8 and spintest:Python 3.6.8

>> pyv D Python-3.6.5
>> pyv rc spintest 
>> pyv l 
** pyv l
# distributions
 from_path:Python 3.6.8:/home/cloud-user/local/pyv/venvs/spintest/bin
*Python-3.6.5:Python 3.6.5:/home/cloud-user/local/pyv/distributions/Python-3.6.5
 Python-3.6.8:Python 3.6.8:/home/cloud-user/local/pyv/distributions/Python-3.6.8

# virtualenvs
 ansible:Python 3.6.8:/home/cloud-user/local/pyv/venvs/ansible
 hermes:Python 3.6.8:/home/cloud-user/local/pyv/venvs/hermes
 iamaas:Python 3.6.8:/home/cloud-user/local/pyv/venvs/iamaas
 sg_hermes:Python 3.6.8:/home/cloud-user/local/pyv/venvs/sg_hermes
*spintest:Python 3.6.8:/home/cloud-user/local/pyv/venvs/spintest

spintest is still present on python 3.6.8

Proposal

on the function _pyv_recreate()
use function _pyv_delete() and _pyv_create()

[ttych]

At the recreation time, the current version is favored against the current selected destributions.
Main scenario, it was made for, is "I reset my complete environment to validate package install + test" keeping the current release.
So :

• pyv rc spintest
• pip install
• ....

In your case either , as you said :

• manually do : pyv d spintest + pyv c spintest
• or pyv rc spintest Python-3.6.8 (adding the expected new version forcing the target python release to be used)