Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    Kal Sze
    Probably something that involves making the python exec print its path and grepping for something in the path that hints at pyenv.
    e.g. grepping for .pyenv/versions/3.9.5/
    Jeremy Cantrell
    Seems like if [[ "$(pyenv global)" == "system" ]]; then would be more robust.
    Kal Sze
    That should also work.
    I mean, it depends on whether you want to determine the python version from within the Python process/script or from a shell script.
    Jeremy Cantrell
    Yeah, you're right. In this case, I just needed to know whether python was the system version or not.
    Eric Dostie
    Hello. I'm seeking help with a hunk failure when patching setup.py when installing Python 2.6.6 via pyenv.
    https://pastebin.com/ug0kDxyM has details. I am ensuring that OpenSSL 1.0.x is being utilized during the install, but I'm not sure that my issue is with OpenSSL. it seems more like an issue with the patch that is being applied to setup.py.
    Eric Dostie
    pyenv doctor is claiming that OpenSSL is not installed, but it clearly is. what gives? https://pastebin.com/VrzrUDvN
    Eric Dostie
    I was able to get pyenv doctor to detect OpenSSL 1.1 successfully (https://pastebin.com/vVzAqj97), but still getting the hunk failure during the install.
    Isaac Ferreira Filho

    Hello everyone. I'm install pyenv and pyenv-virtualenv following instructions in github.

    My problem: I can't access other python versions that I installed through pyenv. I installed version 3.6.9, but when I use pyenv-virtualenv or a "pyenv shell 3.6.9" I'm still on the same version as my system.

    Hi - I've had a look around but aren't able to work out if there's a way to share packages between pyenv virtualenvs? I'm quite keen to avoid a situation where I have 5-10 different copies of torch (~800mb) installed
    would be very grateful for any guidance
    Angus Hollands
    @StephenHogg: not with pyenv + venv - the libraries themselves are installed in conventional Python virtualenvironments
    You can use something like conda, which uses hard-links to avoid duplicating packages (where the versions agree)
    Adam Janik
    CFLAGS="-I$(brew --prefix openssl)/include -I$(brew --prefix readline)/include -I$(xcrun --show-sdk-path)/usr/include" LDFLAGS="-L$(brew --prefix openssl)/lib -L$(brew --prefix readline)/lib -L$(brew --prefix zlib)/lib" CPPFLAGS="-I$(brew --prefix zlib)/include" CONFIGURE_OPTS="--with-openssl=$(brew --prefix openssl)" pyenv install 3.9.1
    But it does not help. Reinstalled zlib, readline and openssl but still does not work on Macos 11.4
    I got no idea how to debug this
    Hi - I need a hand installing python 3.6.9 on arch. I have successfully installed other versions, but less that 3.7 seems to fail. I have a build log, but it is ~10,000 lines. Is there a particular bit of it that would be helpful?
    Jeremy Cantrell
    I just noticed that there are no python, pip, etc symlinks in ~/.pyenv/shims to python3, pip3, etc. Shouldn't those exist? Direnv's pyenv integration looks for "python", so it breaks.
    Xavier Sumba
    hello, I am trying to install python 3.7.11 with pyenv in ubuntu 20 but it is failing due to OpenSSL. I am getting this message The Python ssl extension was not compiled. Missing the OpenSSL lib? I tried what it says in the common build problems guide but can't fix it. Any thoughts ?
    Xavier Sumba
    fixed after installing libssl-dev
    pyenv will cause sh to become stuck due to the eval "$(pyenv virtualenv-init -)" in the configuration file
    Will produce a relatively large freeze
    CentOS dependency yum install -y gcc zlib-devel bzip2-devel readline-devel openssl-devel sqlite-devel curl
    Ubuntu dependency sudo apt install -y gcc zlib1g-dev libbz2-dev libreadline-dev libssl-dev libsqlite3-dev curl
    Highly confusing instructions for first time installer. Section 2 for macOS users, If you use Homebrew to install pyenv you don't have to add any lines to .profile . Correct? So this means you don't need to modify your PATH in anyway? No environmental variables? Thanks for clarification.
    Hi, is it possible to run a script when ever a virtualenv is activated? So i set a local
    virtual env to a directory. When ever i cd into it, the corresponding virtualenv gets activated.
    After that, i like to set an environment variable by a script for example.
    alexbc42: You need pyenv-virtualenv
    Fredrik Averpil

    I have a weird problem. I have a Ubuntu 20.04.3 LTS Live USB and when running it, I cannot install llvm and tk-dev. They are simply not available. I posted an issue here about it: pyenv/pyenv#2076

    Does anyone have any clue as to why I cannot download these two packages?
    In the past, I've downloaded and installed these just fine.

    Sanket Dasgupta

    Man, I hve been using pyenv for so long, I never thought it would break.

    My pyenv activate does everything (sets $VIRTUAL_ENV etc) but fails to set the $PATH any ideas?

    Stefan Ulbrich
    Hi, I installed pyenv yesterday on ubuntu 21.04 (zsh+ OhMyZsh) and everything went fine. When I restarted the PYENV_VERSION variable is always set for each shell (to anaconda) and the local .python-version is ignored. I want anaconda only for jupyter and more recent python versions for development .. I can put an unset PYTHON_VERSION in the rc file but I really wonder where the variable gets set and why
    Also how comes that path and this variable persists even if I remove all traces of pyenv until I restart (log out+in won't do the job)
    Hi there, I want to help with pyenv/pyenv#1527 of pyenv. Can anyone direct me to where to discuss with project maintainers about the style and wordings before making PRs.
    Daniel Shapero
    Having this annoying problem on MacOS Big Sur. I'll fire up a terminal session, do pyenv shell <some python version>, run some code, then go make coffee. When I come back, the machine has gone to sleep, but when I awaken it's as if all the environment variables have been clobbered.
    For example, if I do pyenv shell 3.9.7, then a suspend/resume cycle, then do pyenv version, I get 3.9.7 as the output, but then when I run python3 --version it's clearly picking up my system python (3.8.9).