root@47d430be99fa:~/Projects# openssl version -a OpenSSL 1.0.2g 1 Mar 2016 built on: reproducible build, date unspecified platform: linux-x86_64 options: bn(64,64) rc4(16x,int) des(idx,cisc,16,int) idea(int) blowfish(idx) compiler: gcc -I. -I.. -I../include -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM OPENSSLDIR: "/usr/local/ssl"
$ pyenv --version pyenv 1.2.19-6-gbdfed51
pyenv local 2.7.18), I'm getting
pyenv: version 'x.x.x' not installed:
theia@51a0efa33dd1:/home/project$ ls -l /home/theia/.pyenv/versions/ total 24 drwxr-xr-x 1 theia theia 4096 Aug 6 11:49 2.7.18 drwxr-xr-x 1 theia theia 4096 Aug 6 11:50 3.5.9 drwxr-xr-x 1 theia theia 4096 Aug 6 11:50 3.6.11 drwxr-xr-x 1 theia theia 4096 Aug 6 11:50 3.7.8 drwxr-xr-x 1 theia theia 4096 Aug 6 11:50 3.8.5 drwxr-xr-x 1 theia theia 4096 Aug 6 11:51 3.9-dev theia@51a0efa33dd1:/home/project$ ls -l /home/theia/.pyenv/versions/2.7.18/ total 20 drwxr-xr-x 1 theia theia 4096 Aug 6 11:52 bin drwxr-xr-x 1 theia theia 4096 Aug 6 11:21 include drwxr-xr-x 1 theia theia 4096 Aug 6 11:21 lib drwxr-xr-x 1 theia theia 4096 Aug 6 11:49 man drwxr-xr-x 1 theia theia 4096 Aug 6 11:21 share theia@51a0efa33dd1:/home/project$ pyenv local 2.7.18 pyenv: version `2.7.18' not installed
It seems the issue was that tab completion in the shell was replacing
theia@6c1a368dc9db:/home/project$ ls \~
Putting the full path to the .pyenv folder in my .bashrc seems to have fixed it.
echo 'export PYENV_ROOT="~/.pyenv"' >> ~/.bashrc
echo 'export PYENV_ROOT="/home/theia/.pyenv"' >> ~/.bashrc
❯ pyenv install -vvv pypy3.6-7.3.1 /var/folders/dl/f3h10k2x10l88zy9wdjtbd600000gn/T/python-build.20200908191719.97207 ~/PycharmProjects/typic Downloading pypy3.6-v7.3.1-osx64.tar.bz2... -> https://bitbucket.org/pypy/pypy/downloads/pypy3.6-v7.3.1-osx64.tar.bz2 curl: (22) The requested URL returned error: 404 error: failed to download pypy3.6-v7.3.1-osx64.tar.bz2 BUILD FAILED (OS X 10.15.6 using 0000000000)
I imagine one way is to symlink the global version into the user pyenv dir
Yeah, that's what I've been doing, or just moving them entirely to the user's home directory. I'd like a more correct and automated way of doing it. As it is now, we will seriously clutter the PYENV_ROOT directory.
Hi. Is there a way to upgrade the pip version globally, so that new virtualenvs created use that version? I tried upgrading while having the python version used as base for the envs as global, but creating a venv after that still uses the old pip version.
There is a pyenv plugin that lets you set default installed modules, perhaps it might also upgrade those modules? I'm not sure.
pyenv install --list(latest appears to be
3.9.0-dev). Although I have been loving it so far, I am fairly new to pyenv so I still don't know how new versions become available, is there a PR that needs to happen? I am running the latest pyenv version. Thanks!