Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Mori Bellamy
    @moribellamy
    anyone know why the cpython builds keep what appears to be 60MB+ of test data? e.g. lib/python3.6/test/...
    my pyenv installs weigh roughly 134.4 MB, but the virtualenvs I build off of them weigh about 16MB. was wondering if this is necessary
    Philippe Ombredanne
    @pombredanne
    the sources have these tests. Adding a way to strip them could work, but that would not be using the standard CMMI afaik?
    Mori Bellamy
    @moribellamy
    CMMI?
    Philippe Ombredanne
    @pombredanne
    @moribellamy Configure/Make/Make Install :)
    Mori Bellamy
    @moribellamy
    ah i see. i guess its reasonable to want to treat the build process as opaquely as possible
    if the standard python release process is open enough maybe we could figure out what they do? .dmg's and soforth don't come with all that bloat, maybe its something pyenv could call in to
    AFAIK pyenv doesn't do the "make install" part, so maybe something happens there. but "make install" is kind of antithetical to multiple installations coexisting
    Philippe Ombredanne
    @pombredanne
    Andrew C
    @ntebis
    i am trying to make tcl-tk to work with my mac. I have the 1.2.17 version on my mac and the tcl-tk installed through brew, however I am trying to run the example python -m tkinter -c 'tkinter._test()' but it gives the ModuleNotFoundError: No module named '_tkinter'
    Geordon VanTassle
    @Geordon
    macOS 10.15.4. I use Homebrew for most stuff, since it's nice and easy. I stumbled into a problem that stemmed from having multiple cross-installed Python versions. So, stripped out the versions that I had installed and installed pyenv and installed 3.8.4.
    In order to get pyenv to install 3.8.4, I ended up having to sudo pyenv. IS that how it's supposed to work?
    Angus Hollands
    @agoose77
    @Geordon not afaict
    I'd imagine the install directory pyenv is using has read-only permissions for your user
    Burak Can Kahraman
    @burakcank
    Hi guys, I guess on archlinux installing pyenv package is not enough and some post installation job has to be done right ?
    Burak Can Kahraman
    @burakcank
    I think the regular git installation is preferable but since there is a package I thought it would just execute a post install script or something.
    Burak Can Kahraman
    @burakcank
    Anyone ?
    Burak Can Kahraman
    @burakcank
    Not very active is it :D
    Angus Hollands
    @agoose77
    What's the issue?
    Burak Can Kahraman
    @burakcank
    @agoose77 shims path is not added to the PATH after installing official arch parckage.
    Angus Hollands
    @agoose77
    I'm not an expert on arch, but looking at the package script, it doesn't create any file that gets sourced by your shell. You need to use the Eval step from the binary
    eval "$(pyenv init -)"
    Burak Can Kahraman
    @burakcank
    @agoose77 Yeah apparently I should manually add shims path to my PATH. IMHO the user at least should be notified if something is necessary for pyenv to work correctly following the installation. And again I realized it has nothing to do with pyenv :) Thanks for the answer though !
    TKaluza
    @TKaluza

    Hey there, I wish you a nice day! Thanks for pyenv!

    If I want to build python with optimizations enabled I use for example:
    CONFIGURE_OPTS="--enable-optimizations" pyenv install 3.7.7

    How can I also pass the Information to use multiple cores (like make -j8)? Is this possible?

    aca
    @aca
    Hi everyone, I need some help with pyenv.
    After arch update, pyenv just stopped working.
    It is probably not an issue with pyenv. But I have no idea what's going on.
    Has anyone seen issue like this?
     » pyenv install 3.8.2
    Downloading Python-3.8.2.tar.xz...
    -> https://www.python.org/ftp/python/3.8.2/Python-3.8.2.tar.xz
     Installing Python-3.8.2...
    
    BUILD FAILED (Arch Linux using python-build 20180424)
    
    Inspect or clean up the working tree at /tmp/python-build.20200425123545.346823
    Results logged to /tmp/python-build.20200425123545.346823.log
    
    Last 10 log lines:
    
    
    If you want a release build with all stable optimizations active (PGO, etc),
    please run ./configure --enable-optimizations
    
    
    gcc -pthread -c -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall    -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration  -I./Include/internal  -I. -I./Include -I/home/rok/.pyenv/versions/3.8.2/include  -I/home/rok/.pyenv/versions/3.8.2/include   -DPy_BUILD_CORE -o Programs/python.o ./Programs/python.c
    make: gcc: Permission denied
    make: *** [Makefile:772: Programs/python.o] Error 127
    make: *** Waiting for unfinished jobs....
    Burak Can Kahraman
    @burakcank
    Have you tried doing the suggested clean up ? @aca
    No problem on my side, using arch and pyenv works just fine.
    k
    @denekthanyjana_twitter

    I have been using pyenv for managing python versions and virtual environments on my mac for some time now.
    Recently I reinstalled pyenv and since then on every pyenv command I try to run, I get the following error

    /usr/local/bin/pyenv:94: command not found: shopt

    My default shell is the latest MacOS's default shell i.e. zsh.
    On searching for the fix, I found out it has something to do with bash interfering with the zsh.
    My default shell is zsh in settings, the contents of ~/.bash_profile, /etc/profile & /etc/bashrc are all commented out but I am still having the issue.
    My OS Verion is: 10.15.4.
    I tried reinstalling pyenv as well but I am getting the same error.
    I am unable to run ANY pyenv related command, can anyone please help? Is this a pyenv issue?

    k
    @denekthanyjana_twitter
    Should I create an issue on github? If there's no solution to this?
    Burak Can Kahraman
    @burakcank
    try running it within bash and maybe try running shopt itself ?
    @denekthanyjana_twitter ^
    k
    @denekthanyjana_twitter
    hi @burakcank, when I switch to bash and run shopt, I can see the command exists but when I run any pyenv command, it gives the exact same error.
    Burak Can Kahraman
    @burakcank
    Your problem sounds exactly similar to the problem in this link and the suggested solution is probably what you are looking for.
    Burak Can Kahraman
    @burakcank
    adding export PATH=/usr/local/bin:$PATH to your .zshenv would probably solve your issue.
    basically you need to make sure zsh is able to reach to locations where other programs are installed.
    k
    @denekthanyjana_twitter

    @burakcank I switched to bash as shopt command was working in bash, and I added

    export PATH=/usr/local/bin:$PATH

    as the first line in my ~/.bash_profile, but I still got the same error. i.e.

    /usr/local/bin/pyenv:94: command not found: shopt

    As you can see it's not having trouble finding the pyenv command, pyenv command is there in /usr/loca/bin and the terminal is picking it up from there from $PATH, the problem is in pyenv not being able to find the shopt command it seems like, when shopt command is there as I can see by running shopt on the terminal.

    Burak Can Kahraman
    @burakcank
    @denekthanyjana_twitter I am assuming you have restarted your pc after modifying your bash_profile or sourced it in the same shell session right ?
    Burak Can Kahraman
    @burakcank
    Quote "shopt is not a command, but a shell built-in. bash knows what to do with it because it's a bash built-in , but zsh has no idea what it is. You'll want to look into setopt which is a zsh Built-in, and put those values into a new .zshrc script."
    I realized after running which shopt which failed for obvious reasons and came across with this.
    Burak Can Kahraman
    @burakcank
    It's interesting that pyenv is trying to use a built-in command for bash. Basically pyenv is not aware that you are using zsh instead of bash in the first place.
    So this is the first thing you should solve I guess.
    k
    @denekthanyjana_twitter

    @denekthanyjana_twitter I am assuming you have restarted your pc after modifying your bash_profile or sourced it in the same shell session right ?

    yes of course, i sourced it, even restarted terminal. Did not restart PC though, as that might be an overkill.

    It's interesting that pyenv is trying to use a built-in command for bash. Basically pyenv is not aware that you are using zsh instead of bash in the first place.

    as I mentioned above, I am having this problem with bash as well. I tried all of the above with bash. I am using bash, pyenv should work with that at least. I don't understand why pyenv is unable to find shopt command (if it uses it) when I can easily see it in my bash terminal)

    I realized after running which shopt which failed for obvious reasons and came across with this.

    instead of which shopt, just do shopt and you will see. Although that will only work in bash terminal, as it's a bash built-in command.

    Burak Can Kahraman
    @burakcank
    @denekthanyjana_twitter based on your installation process pyenv might be trying to spawn a zsh session and find shopt in there. We don't know what pyenv is doing, and since you haven't restarted your pc and only sourced bash_profile in your terminal it does not alter your environment for all of the bash sessions at all. When you change ~/.bash_profile you should restart your pc for it to take effect for all bash processes, because .bash_profile gets sourced when you login, you should at least logout and login.
    @denekthanyjana_twitter As best practice if you are using zsh as default, let's try to solve the problem through zsh and not bash. You won't be spawning bash just for pyenv.
    k
    @denekthanyjana_twitter

    Okay @burakcank, zsh it is then.
    I restarted my mac as you said.
    Here's the output of my $ echo $PATH

    /usr/local/opt/openssl@1.1/bin:/Users/abc/Library/Python/3.7/bin:/usr/local/Cellar/postgresql@9.6/9.6.16/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/abc/bin:/usr/local/opt/rabbitmq/sbin

    As you can see /usr/local/bin is there which is the location of pyenv. Still having the same problem.

    19 replies
    Angus Hollands
    @agoose77
    This message was deleted
    Niraj Lama
    @narwen_niraj_twitter
    Hi I have followed every step from github
    but when I try to see my python version it is still in the default of the mac os