Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Burak Can Kahraman
    @burakcank

    For me though :( my distro doesnt ship a python executable anywhere in the path like /usr/bin
    ships with /usr/bin/python3 and /usr/bin/python2 though

    Just symlink python to python2 or python3 based on your preference.

    Oh sorry didn't see the next post.
    If there wasn't any python link before, it shouldn't be an issue.
    Philippe Ombredanne
    @pombredanne
    it is uncommon not to have a /usr/bin/python
    Burak Can Kahraman
    @burakcank
    ❯ pyenv shell system
❯ which python
/home/kent/.pyenv/shims/python
❯ pyenv which python
/usr/bin/python

    Is that unexpected behaviour?

    This is how I use pyenv too, seemed like totally fine to me. You access system python through a shim.

    Kent Brockman
    @KentBrockman
    thanks for the tips guy...seems like that one is the winner for sure
    and yeah philippe I agree. this seems to be a common thing in ubuntu (common enough that theres a whole package for...applying this symlink tweak: https://ubuntu.pkgs.org/20.04/ubuntu-main-armhf/python-is-python3_3.8.2-4_all.deb.html
    @burakcank I seem to be missing a system pip install as well...do you symlink /usr/bin/pip3 ?
    Burak Can Kahraman
    @burakcank
    No I do actually have pip, not the symlink but that's the way to go for you apparently.
    Kent Brockman
    @KentBrockman
    alright
    Philippe Ombredanne
    @pombredanne
    :)
    Yan Wong
    @hyanwong
    I'm trying to run a python version within the gdb debugger, that's been compiled by pyenv on OS X with the --debug flag: pyenv install --debug 3.9-dev. But when I run sudo gdb /path/to/.pyenv/versions/3.9-dev-debug/bin/python3.9d I get 
    Reading symbols from /path/to/.pyenv/versions/3.9-dev-debug/bin/python3.9d...

warning: `/private/var/folders/00/l36df9q14hv13hhw8wglncch0000gr/T/python-build.20201201132008.47447/Python-3.9-dev/Programs/python.o': can't open to read symbols: No such file or directory.

warning: Could not open OSO archive file "/private/var/folders/00/l36df9q14hv13hhw8wglncch0000gr/T/python-build.20201201132008.47447/Python-3.9-dev/libpython3.9d.a"
(No debugging symbols found in /path/to/.pyenv/versions/3.9-dev-debug/bin/python3.9d)
    Is this possible - I can't find any information on the web about how to do this using pyenv-installed python binaries?
    dennisetiawan23
    @dennisetiawan23
    Hello , i want to install pyenv in my school server directories
    but i dont have apt-get, or curl, and sudo access
    is this possible?
    Philippe Ombredanne
    @pombredanne
    @dennisetiawan23 this is a local, user-only install
    as long as you have the essential build and toolchain parts already installed (as well as a few common basics like zlib, bzip2, xz and a few similar)
    Try it :)
    @hyanwong if I were trying to debug a Python interpreter, I would likely build myself
    Yan Wong
    @hyanwong
    Thanks. I resorted to that, but it would be nice not to have to!
    Philippe Ombredanne
    @pombredanne

    @hyanwong that's IMHO a too exotic and rare a use case to ever support this

    If you are in a state advanced enough that you are debugging an interpreter, you should not need any of pyenv IMHO

    Dilum Aluthge
    @DilumAluthge
    I'm trying to build Python 3.8.6 with Framework support on macOS, and it is trying to write to /Applications. Can I instead write to a different folder, e.g. ~/Applications or something like that?
    I found this issue (pyenv/pyenv#1468) with the same request, but there is no answer there.
    Nafiul Islam
    @gamesbrainiac_twitter
    Folks, any idea when python 3.10a6 is going to be installable?
    Chris Barnes
    @clbarnes
    when this PR is merged pyenv/pyenv#1839
    Ryan Delaney
    @rpdelaney
    pyenv builds break when the PYENV_ROOT path contains whitespace. Known issue?
    I get the (arguably unhelpful) error that "C compiler cannot create executables"
    Ryan Delaney
    @rpdelaney
    I am not confident I can exhaustively search the closed issues to confirm there is nothing about this in there, but if folks here think it's a bug then I will file one
    Ryan Delaney
    @rpdelaney
    Is it possible that this bug is with python? I have not attempted to build python except with pyenv
    Philippe Ombredanne
    @pombredanne
    @rpdelaney Python never liked spaces in the install path
    in general I would strongly discourage spaces in any paths :)
    Ryan Delaney
    @rpdelaney
    Yeah, unfortunately macOS defaults don't follow this
    Jerry Morrison
    @1fish2
    An empty path element can also cause build errors that are hard to debug, e.g. from a startup script that does export CPATH=foo/include:$CPATH before $CPATH gets set.
    It'd save a lot of debugging headaches if pyenv checked for bad paths, libraries required to build python that are missing from the paths, and other known problems.
    Philippe Ombredanne
    @pombredanne
    @1fish2 is this something you would know how to code?
    Jerry Morrison
    @1fish2
    @pombredanne I'm happy to help but this looks beyond my bash skills, pyenv/plugins/python-build/bin/python-build?
    Ryan Delaney
    @rpdelaney
    I'm reasonably comfortable in bash. If someone can point me in a direction I might be able to at least add a check for paths containing whitespace, newlines, or glob characters
    Although the latter is somewhat dependent on shell settings
    I'd suggest simply printing a warning message that the build may fail in case this behavior ever changes upstream
    Jerry Morrison
    @1fish2

    I dug up some history on that empty path element problem.

    Reasonable-looking shell startup code export C_INCLUDE_PATH="${C_INCLUDE_PATH}:${TEAM_HOME}/usr/local/include" ran before anything set C_INCLUDE_PATH, thus setting it to :/share/team/usr/local/include". gcc interprets that as .:/share/team/usr/local/include" which loaded the wrong include file and led to an obscure error message.

    Mark Harris
    @SiliconMeeple
    Hopefully this will sound familiar to someone. I had pyenv installed on ubuntu 20.04 (probably), and a number of successful very usable python installations. I've since updated to 20.10 (or possibly done something else) and now python install anything fails with the below error message.
    I've re-installed pyenv via brew and checked that I've got all the listed python build dependencies (https://github.com/pyenv/pyenv/wiki#suggested-build-environment).
    Unfortunately, every time I run python install for any version, it fails with the following error.
    Any thoughts or advice on how to fix or troubleshoot the problem would be gratefully received:
    
Downloading Python-3.6.11.tar.xz...
-> https://www.python.org/ftp/python/3.6.11/Python-3.6.11.tar.xz
Installing Python-3.6.11...

BUILD FAILED (Ubuntu 20.10 using python-build 20180424)

# ... snipped to last few loglines:

    esac; \
     ./python -E -m ensurepip \
        $ensurepip --root=/ ; \
fi
Aborted (core dumped)
make: *** [Makefile:1102: install] Error 134
    Philippe Ombredanne
    @pombredanne
    :| weird for sure
    @SiliconMeeple pyenv/pyenv#1621 ?
    Mark Harris
    @SiliconMeeple
    Following the advice there fixed it! Thank you very much. :-)
    Philippe Ombredanne
    @pombredanne
    :+1:
    Jon Crall
    @Erotemic
    Is there any way to use pyenv (or some other tool) to fetch precompiled python binaries for specific versions? I'm trying to replace conda in my workflow, and the compile time of pyenv is currently a limiting factor in how fast I can setup a machine. Any tips?
    Philippe Ombredanne
    @pombredanne
    @Erotemic pyenv only and exclusively builds from sources.
    You want to look for prebuilt binary packages instead of pyenv (or build your own) ... which OS?
    Jon Crall
    @Erotemic
    Ideally, any modern 64 bit OS, but it would be fine with just x86_64 linux. One of the use cases is that I'm trying to walk non-technical users through installing a Python application. They don't have much patience for compiling code, and sometimes they don't even have the ability to use sudo to install the deps like build-essential. I was using conda to achieve this, but they've changed their license such that it makes it hard to provide a reliable and truly FOSS solution. The other use case that I mentioned is just setting up a machine quickly without having to compile (and pgo optimize) python. (Maybe there is a way to use Conan to do this? I'm not super familiar with the system, so I'm not sure exactly what you can do with it).
    ashwinvis
    @ashwinvis:matrix.org
    [m]
    I made this pyenv plugin recently, which could be useful if you use pyenv-virtualenv and wish to upgrade your virtual environments to a different Python compiler version https://github.com/ashwinvis/pyenv-virtualenv-migrate/. Feedback welcome 🙂