Comment 17 for bug 1301618

Thanks for the bug report!

The pyvenv error is interesting, and will take some further investigation.

The package conflict is by design. There are multiple file conflicts between the two packages. We had two options: remove/rename every generic file (/usr/bin/python3, /usr/bin/pydoc3, /usr/bin/pyvenv, etc.), or explicitly conflict the various versions of python3 we offer. We felt that not having python3 command would be more confusion than it was worth.