Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Emil Stenström
    @EmilStenstrom
    I agree that the problem likely has nothing to do with pyenv. Let me know if I should just go away :)
    I'm using pyenv from homebrew, with the exact same steps in the tutorial you posted above
    Here's a full log of ./configure --with-pydebug: https://gist.github.com/EmilStenstrom/6300655c46b1640de1b720be732a4652
    Philippe Ombredanne
    @pombredanne

    Let me know if I should just go away :)

    not at all :P

    Philippe Ombredanne
    @pombredanne
    ok, configure runs fine, now using the same thing, run make and past the whole ouput
    Emil Stenström
    @EmilStenstrom
    Here's a full log of ./make -d (debug mode): https://gist.github.com/EmilStenstrom/8eb1185fba582058e562c66d5fbf2a07
    Emil Stenström
    @EmilStenstrom
    Ok, so here's something interesting... If I remove my .bash_profile, it builds...
    Emil Stenström
    @EmilStenstrom
    YES! Solved. The problem was that I had overridden the diff-command with colordiff from git-core. Had this in my .bash_profile
    # Improved diff: Use diff-highlight to show word-level differences
    # Required: brew install colordiff
    PATH="/usr/local/opt/git/share/git-core/contrib/diff-highlight/:$PATH"
    function diff {
      /usr/bin/diff -u -b "$@" | colordiff | diff-highlight
    }
    export -f diff
    Philippe Ombredanne
    @pombredanne
    @EmilStenstrom :+1:
    Emil Stenström
    @EmilStenstrom
    thanks for suggesting to try with the tarball, helped my narrow it down
    Philippe Ombredanne
    @pombredanne
    @EmilStenstrom my pleasure :)
    Chris Barnes
    @clbarnes
    hi all! I was wondering if I'm alone in missing named versions for miniconda > 4.3.30; continuum has up to 4.6.14 by now
    i've done a pyenv update, and a git pull in my ~/.pyenv/
    anaconda seems to have been kept updated so it seemed odd that miniconda stopped in 2017
    Philippe Ombredanne
    @pombredanne
    @clbarnes :wave: ... I think miniconda was waiting for you to add new versions to https://github.com/pyenv/pyenv/tree/master/plugins/python-build/share/python-build ;)
    Chris Barnes
    @clbarnes
    aha! is there any documentation on how to add builds, and then test they work? or will i get away with copying and pasting, changing a few URLs?
    Chris Barnes
    @clbarnes
    pyenv/pyenv#1361 PR based on above strategy
    Philippe Ombredanne
    @pombredanne
    @clbarnes :bow:
    Chris Barnes
    @clbarnes
    well, miniconda was waiting ;)
    Scott Colby
    @scolby33

    I'm having some difficulty building with --with-lto on macOS 10.14.5:

    $ env PYTHON_CONFIGURE_OPTS="--enable-optimizations --enable-ipv6 --with-lto" pyenv install 3.7.2
    python-build: use openssl from homebrew
    python-build: use readline from homebrew
    Downloading Python-3.7.2.tar.xz...
    -> https://www.python.org/ftp/python/3.7.2/Python-3.7.2.tar.xz
    Installing Python-3.7.2...
    python-build: use readline from homebrew
    python-build: use zlib from xcode sdk
    
    BUILD FAILED (OS X 10.14.5 using python-build 20180424)
    
    Inspect or clean up the working tree at /var/folders/v3/vz516bnx0tg1zg3rflqt8v740000gn/T/python-build.20190709125708.4682
    Results logged to /var/folders/v3/vz516bnx0tg1zg3rflqt8v740000gn/T/python-build.20190709125708.4682.log
    
    Last 10 log lines:
    checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p
    checking for --with-pydebug... no
    checking for --with-assertions... no
    checking for --enable-optimizations... yes
    checking for --with-lto... yes
    checking target system type... x86_64-apple-darwin18.6.0
    checking for -llvm-ar... no
    checking for llvm-ar... ''
    configure: error: llvm-ar is required for a --with-lto build with clang but could not be found.
    make: *** No targets specified and no makefile found.  Stop.

    Has anyone seen this before?

    Angus Hollands
    @agoose77
    I havne't seen it before
    @scolby33 have you tried installing the missing package?
    Scott Colby
    @scolby33
    At least via homebrew, llvm-ar isn't available standalone. I think I would have to install the entire llvm/clang toolchain from brew and use that, but I remain curious why this doesn't work with the system toolchain.
    Philippe Ombredanne
    @pombredanne
    @scolby33 why do you ask the --lto option?
    if you ask for lto, I would guess that some intermediate .a is built, and therefore when you use llvm you would need llvm ar ?
    Scott Colby
    @scolby33
    In fact I don't really need LTO here, but I was playing with it and am trying to figure out why this doesn't work.
    A solution that seems to work is to go ahead and install llvm from Homebrew and specify the LLVM_AR environment variable
    $ env PYTHON_CONFIGURE_OPTS="--enable-optimizations --enable-ipv6 --with-lto" LLVM_AR=/usr/local/opt/llvm/bin/llvm-ar CPPFLAGS='-I/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include' CFLAGS='-I/usr/local/opt/sqlite/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include' LDFLAGS='-L/usr/local/opt/sqlite/lib' pyenv install 3.7.4 --verbose
    (The reason I was messing with this at all was that I needed to link to a newer sqlite.)
    I believe I have also found a bug in pyenv, which I'll report on Github if it's not clearly something I'm doing wrong:
    $ env PYTHON_CONFIGURE_OPTS="CFLAGS='-I/usr/local/opt/sqlite/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include'" pyenv install 3.7.2
    python-build: use openssl from homebrew
    python-build: use readline from homebrew
    Downloading Python-3.7.2.tar.xz...
    -> https://www.python.org/ftp/python/3.7.2/Python-3.7.2.tar.xz
    Installing Python-3.7.2...
    python-build: use readline from homebrew
    python-build: use zlib from xcode sdk
    
    BUILD FAILED (OS X 10.14.5 using python-build 20180424)
    
    Inspect or clean up the working tree at /var/folders/v3/vz516bnx0tg1zg3rflqt8v740000gn/T/python-build.20190710153459.77443
    Results logged to /var/folders/v3/vz516bnx0tg1zg3rflqt8v740000gn/T/python-build.20190710153459.77443.log
    
    Last 10 log lines:
    /var/folders/v3/vz516bnx0tg1zg3rflqt8v740000gn/T/python-build.20190710153459.77443 ~/dev/mayhemdb/api
    /var/folders/v3/vz516bnx0tg1zg3rflqt8v740000gn/T/python-build.20190710153459.77443/Python-3.7.2 /var/folders/v3/vz516bnx0tg1zg3rflqt8v740000gn/T/python-build.20190710153459.77443 ~/dev/mayhemdb/api
    configure: error: unrecognized option: `-I/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include''
    Try `./configure --help' for more information
    make: *** No targets specified and no makefile found.  Stop.
    Somehow the closing single quote gets included in the option.
    Scott Colby
    @scolby33

    If I swap " to ' and ' to " it's the same problem just with the error

    configure: error: unrecognized option: `-I/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include"'

    note the lone double quote after include.

    Alexandre Assouad
    @t0k4rt
    Hello, Guys, does pyenv changed the way it symlinks python version in latest pyenv versions ? I use pyenv install 3.6.8 on mac Osx 10.14.5 and it only produces symlinked python3 bin but no python symlink is created. Is it normal ? it created also only one pip3 but no more pip. Has anybody experienced this ? Thanks for your help !
    Paul Ganssle
    @pganssle
    I spent a bit of time trying to understand how the python-build plugin works to try and answer this question for myself, but I figured I'd just ask in here instead: Does pyenv use make -j (I think it might use make -j1, but I didn't totally understand the code where I saw that), and if not is there a way to configure it so that it does?
    Angus Hollands
    @agoose77
    Hey all, I'm trying to run pyenv commands from a subprocess, and it's not picking up the virtualenv by setting PYENV_VERSION. Does anyone have any ideas why?
    Angus Hollands
    @agoose77
    It turned out that running using the "system" python placed the system binaries directory at the front of path, so I wasn't using the shims
    Philippe Ombredanne
    @pombredanne
    :)
    Chris Barnes
    @clbarnes
    how do you do functional/integration tests of changes you make to pyenv? i have a PR up which adds a bunch of new versions but don't know the best way to test them
    (16 different miniconda versions, to be exact)
    FifteenOUC
    @FifteenOUC
    Hi,Guys! I have installed pyenv and Python3.9-dev suceessfully. However, when I try to include Python.h in my C files, the GCC can not find "Python.h". Does anyone know how to fix it?(MacOS)
    Jack Haden-Enneking
    @jacktose
    Looks like the github wiki was vandalized. Pages are replaced with "delete" or fully deleted.
    Philippe Ombredanne
    @pombredanne
    and that looks fixed now :)
    George Nachman
    @gnachman_twitter
    I need to build a completely static Python for redistribution, including (for example) the ssl module. Is this possible with pyenv?
    Yung-Jin (Joey) Hu
    @TheGhostHuCodes

    Hi All, I recently upgrade pyenv using brew, and it installed pyenv-1.2.13_1; looks like the _1 is a revision. After that I get this error when trying to use a shimmed python:

    $ python
    /Users/me/.pyenv/shims/python: line 21: /usr/local/Cellar/pyenv/1.2.13/libexec/pyenv: No
    such file or directory

    I can fix this by going into /Users/me/.pyenv/shims/python and adding the _1 to line 21:

    exec "/usr/local/Cellar/pyenv/1.2.13/libexec/pyenv" exec "$program" "$@"

    Is there a way to fix this without editing this file? Is this a bug that I should report to pyenv, or to brew?

    Akhil Lawrence
    @akhilputhiry
    Hi folks, when will the 3.8.0 be made available
    Angus Hollands
    @agoose77
    @akhilputhiry I think it's available now, no?
    I see it in pyenv versions -l
    abz123
    @abz123

    Hello all,
    help needed with error message.

    OS:
    ↳ cat /etc/os-release
    NAME="Linux Mint"
    VERSION="19.1 (Tessa)"
    ID=linuxmint
    ID_LIKE=ubuntu
    PRETTY_NAME="Linux Mint 19.1"
    VERSION_ID="19.1"
    HOME_URL="https://www.linuxmint.com/"
    SUPPORT_URL="https://forums.ubuntu.com/"
    BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
    PRIVACY_POLICY_URL="https://www.linuxmint.com/"
    VERSION_CODENAME=tessa
    UBUNTU_CODENAME=bionic

    Terminal:
    zsh/tmuxp/vim

    installed pyenv and was able to use as normal.
    Recently started to see error messages when accessing the following:
    ↳ tmuxp load Public/js/vue/vue-docs/vue.yaml

    Message1:
    Unable to rehash.
    Dont have a copy of it but i think it was referencing /.pyenv/versions/3.7.2/.........
    However, it was still possible to launch tmuxp session.

    Message2:
    Once message 1 stopped this began to print:
    ↳ tmuxp load Public/js/vue/vue-docs/vue.yaml
    zsh: /home/ab2qik/.local/bin/tmuxp: bad interpreter: /home/ab2qik/.pyenv/versions/3.7.2/envs/venv3.7.2/bin/python3.7: no such file or directory
    Now no longer possible to launch tmuxp session.

    ↳ pyenv versions
    system
    3.7.2
    3.7.2/envs/v-372
    3.8-dev
    3.8-dev/envs/v-38-dev

    • v-372 (set by /home/ab2qik/.python-version)
      v-38-dev

    ↳ python -V
    Python 3.7.2

    Thankyou

    abz123
    @abz123

    git cloned it.

    ↳ cat /etc/zsh/zshenv

    /etc/zsh/zshenv: system-wide .zshenv file for zsh(1).

    #

    Global Order: zshenv, zprofile, zshrc, zlogin

    if [[ -z "$PATH" || "$PATH" == "/bin:/usr/bin" ]]
    then
    export PATH="/usr/local/bin:/usr/bin:/bin:/usr/games"
    fi

    env variable = PYENV_ROOT

    export PYENV_ROOT="$HOME/.pyenv"
    export PATH="$PYENV_ROOT/bin:$PATH"

    tmuxp completion

    eval "$(_TMUXP_COMPLETE=source tmuxp)"

    Auto activation/deactivation of virtualenvs. Works with shell specific python version selection

    eval "$(pyenv virtualenv-init -)"

    add pyenv init to shell

    #

    eval "$(pyenv init -)"

    if command -v pyenv 1>/dev/null 2>&1; then
    eval "$(pyenv init -)"
    fi