..........
robin@minikat:~/devel/reportlab
$ $HOME/LOCAL/3.9b1/bin/python3.9
Python 3.9.0b1 (default, May 19 2020, 12:50:30) [GCC 10.1.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
import distutils
/home/robin/LOCAL/3.9b1/lib/python3.9/distutils/__init__.py:15: UserWarning:
The virtualenv distutils package at %s appears to be in the same location as
the system distutils?
warnings.warn("The virtualenv distutils package at %s appears to be in the same
location as the system distutils?")
distutils.__path__
['/home/robin/LOCAL/3.9b1/lib/python3.9/distutils']
distutils.__file__
'/home/robin/LOCAL/3.9b1/lib/python3.9/distutils/__init__.py'
is this a bug or have I built python 3.9.0b1 wrongly?
I think that is correct __file__ value. What are you expecting to see?
I wasn't expecting the warning at all, but in fact this appears to be an interaction caused by installing
virualenv==16.2.0 into my home built python3.9.0b1 and then using it to create a virtual environment. For some reason
that creates a problem in the base python which I haven't yet fully explained.
I can build python3.9.9b1 virtualenvs using archlinux python 3.8.2 with
/bin/python -mvirtualenv -p /home/robin/LOCAL/3.9b1/bin/python3.9 myenv
I prefer the older virtualenv because it makes python executables which I can link to rather than always using an
explicit path.
Sorry for the noise.
Barry
--
Robin Becker
--
https://mail.python.org/mailman/listinfo/python-list
O
--
https://mail.python.org/mailman/listinfo/python-list
