On 27/12/2020 04.05, songbird wrote:
> songbird wrote:
> ...
>> The package mentioned is installed:
>>
>>
>> =
>>
>> $ dpkg -l | grep python3-venv
>> ii python3-venv 3.9.0-4
>> amd64pyvenv-3 binary for python3 (default python3 version)
Chris Angelico wrote:
> On Mon, Dec 28, 2020 at 2:56 AM songbird wrote:
...needed to pull a few more things from unstable...
> Ah, yep, that makes sense. I was a tad concerned about the mismatch of
> versions, but honestly, I don't think I've ever installed Python from
> testing or unstable (unles
On Mon, Dec 28, 2020 at 2:56 AM songbird wrote:
>
> Chris Angelico wrote:
>
> ok, i got it to work. i noticed that there was a 3.8
> version of distutils that was not upgraded to 3.9 so once
> i specifically pulled that in from the unstable Debian
> distribution then it upgraded and my creation
Chris Angelico wrote:
ok, i got it to work. i noticed that there was a 3.8
version of distutils that was not upgraded to 3.9 so once
i specifically pulled that in from the unstable Debian
distribution then it upgraded and my creation of a new
virtual environment would work without errors.
so
songbird wrote:
...
> The package mentioned is installed:
>
>
>=
>
> $ dpkg -l | grep python3-venv
> ii python3-venv 3.9.0-4amd64
>pyvenv-3 binary for python3 (default python3 version)
>
here is something i missed including in my fi
Chris Angelico wrote:
...
> $ which python
/usr/bin/python for both user and root
looking at /usr/bin it looks like:
lrwxrwxrwx 1 root root 7 Nov 3 03:20 python -> python3
lrwxrwxrwx 1 root root 9 Dec 6 05:36 python3 -> python3.9
-rwxr-xr-x 1 root root 5479
On Sun, Dec 27, 2020 at 11:31 AM songbird wrote:
>
>
> Simlar to Rich's asking about how to deal with python3.9
> I'm not able to to get my virtual environment set up to work
> now and I'm not sure how to go about fixing this.
>
> As it is testing I may have broken it somehow but I do not
> kn
Simlar to Rich's asking about how to deal with python3.9
I'm not able to to get my virtual environment set up to work
now and I'm not sure how to go about fixing this.
As it is testing I may have broken it somehow but I do not
know how to fix this.
I asked on the Debian user mailing list
