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 ?
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?
but i dont have apt-get, or curl, and sudo access
is this possible?
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
I found this issue (pyenv/pyenv#1468) with the same request, but there is no answer there.
I get the (arguably unhelpful) error that "C compiler cannot create executables"
in general I would strongly discourage spaces in any paths :)
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.
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
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.
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
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
Any thoughts or advice on how to fix or troubleshoot the problem would be gratefully received:
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
@SiliconMeeple pyenv/pyenv#1621 ?
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).
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 🙂
@Erotemic
The first thing that comes to mind as you seem to be on some Debian linux or derivative (you mentioned buidl-essential) would be the deadsnakes PPA https://launchpad.net/~deadsnakes to get a binary Python package for a given Python version. This would require sudo though.
The second thing that comes to mind in your case and that could be Linux-distro independent would be AppImage, but that might imply you may need to do the packaging in the first place? there may be some Python appimages to reuse.
https://appimage.org/ and https://appimage.github.io/apps/ ?
Snaps and flatpack are of the same style.
AppImage does NOT require root
@Erotemic there are pretty awesome. Linus picked that for installation of his dive log app
https://subsurface.github.io/download/
https://subsurface.github.io/download/