profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/joshfriend/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Josh Friend joshfriend @MichiganLabs Grand Rapids Michigan

jacebrowning/memegen 700

The free and open source API to generate memes.

jacebrowning/template-python 491

A template for new Python libraries.

citizenlabsgr/elections-api 7

API for voter registration status and sample ballots in Michigan.

jacebrowning/dropthebeat 6

Music sharing using Dropbox.

joshfriend/bunnypedia 3

A companion guide to the card game Killer Bunnies

joshfriend/arm-project-template 1

Bare metal setup for ARM projects. Includes a makefile, linker scripts, and startup files

joshfriend/atlas 1

Webhook bot to integrate Atlassian products such as JIRA with Slack.

startedasottile/pyupgrade

started time in 8 hours

issue closedpyenv/pyenv

OSX - Install in custom Applications directory

By default pyenv installs in /Applications directory. I have a work laptop in which I can only install applications in /Users/vikas027/Applications.

Is there an option to install in /Users/vikas027/Applications rather than /Applications directory.

➜  ~ pyenv install -v 3.7.3
<redacted>
Last 10 log lines:
cp ./../Icons/PythonLauncher.icns  "Python Launcher.app/Contents/Resources"
cp ./../Icons/PythonSource.icns  "Python Launcher.app/Contents/Resources"
cp ./../Icons/PythonCompiled.icns  "Python Launcher.app/Contents/Resources"
cp ./factorySettings.plist  "Python Launcher.app/Contents/Resources"
cp -R ./English.lproj "Python Launcher.app/Contents/Resources"
test -d "/Applications/Python 3.7" || mkdir -p "/Applications/Python 3.7"
mkdir: /Applications/Python 3.7: Permission denied
make[2]: *** [install] Error 1
make[1]: *** [install_PythonLauncher] Error 2
make: *** [frameworkinstallapps] Error 2
➜  ~

closed time in 11 hours

vikas027

issue commentpyenv/pyenv

OSX - Install in custom Applications directory

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

vikas027

comment created time in 11 hours

push eventpyenv/pyenv

Ned Batchelder

commit sha 5f751985696ce20b069fdbe8426657df20ee41c3

Add 3.10.0b3 (#1988) * Add 3.10.0b3 Co-authored-by: Ivan Pozdeev <vano@mail.mipt.ru>

view details

push time in 11 hours

PR merged pyenv/pyenv

Add 3.10.0b3

This simply copies and updates the 3.10.0b2 recipe.

Make sure you have checked all steps below.

Prerequisite

  • [ ] Please consider implementing the feature as a hook script or plugin as a first step.
    • pyenv has some powerful support for plugins and hook scripts. Please refer to Authoring plugins for details and try to implement it as a plugin if possible.
  • [ ] Please consider contributing the patch upstream to rbenv, since we have borrowed most of the code from that project.
    • We occasionally import the changes from rbenv. In general, you can expect changes made in rbenv will be imported to pyenv too, eventually.
    • Generally speaking, we prefer not to make changes in the core in order to keep compatibility with rbenv.
  • [ ] My PR addresses the following pyenv issue (if any)
    • Closes https://github.com/pyenv/pyenv/issues/XXXX

Description

  • [ ] Here are some details about my PR

Tests

  • [ ] My PR adds the following unit tests (if any)
+2 -2

0 comment

1 changed file

nedbat

pr closed time in 11 hours

issue commentpyenv/pyenv

How to install pyenv system-wide

But this seems seems to want to use the PYENV_ROOT and seems klinda hard-coded, if I'm seeing correctly.

https://github.com/pyenv/pyenv-virtualenv/blob/294f64f76b6b7fbf1a22a4ebba7710faa75c21f7/bin/pyenv-virtualenv#L356

That's Pyenv-Virtualenv's problem, create an issue there.

Strictly speaking. PYENV_ROOT doesn't need to be where the pyenv executable is installed. E.g. in MacOS Homebrew, Pyenv is installed into $(brew --prefix) while user files are still under ~/.pyenv. However, alternative Python versions and shims are expected to be found under PYENV_ROOT -- so if you set it to ~/.pyenv, you won't see the alternative versions installed system-wide.

albireox

comment created time in 12 hours

issue commentpyenv/pyenv

Provide shims for micro/patch releases (python3.7.4)

Welp, I didn't mean to.

I would expect to need to reference the version in a pyenv global call

I don't really follow how the third segment of the version is so utterly silly to want while the second segment is regular normal functionality for pyenv.

That's because python, pythonX and pythonX.Y (but not pythonX.Y.Z) is an existing established standard, https://www.python.org/dev/peps/pep-0394/, that Pyenv follows due to it being the standard way of providing Python in UNIX-like systems.

The reason why it doesn't provide micro release executables is because they are source- and binary-compatible, unlike minor ones, so there's no reason to have more than one available at the same time as part of an OS installation, as is there no need to write general-purpose software (=software that would expect to be installed into such an environment) that strictly expects a specific micro release.

As a consequence, users don't expect pytonX.Y.Z to be present on a system -- thus don't write software that expects or needs it, and Python's makefiles and OS packages don't create them. So there's no use case for this feature that would warrant the added complexity and maintenance cost -- at least, none has been presented so far.

altendky

comment created time in 12 hours

issue commentpyenv/pyenv

How to install pyenv system-wide

Thank you @albireox for your feedback. That's a good idea to just use good old virtualenv (without the pyenv plugin). I'll play around with that and see if it will work for my use-case. Thanks again

albireox

comment created time in a day

issue closedpyenv/pyenv

`compctl` does not fallback to filename completion

In zsh, pyenv autocomplete behavior does not have a fallback. Normally it should fallback to filename completion, e.g.

pyenv exec ~/D\tab

# should complete ~/D with possible filenames

This may due to the line below.

https://github.com/pyenv/pyenv/blob/d08c9cfb362c5a7e18a92acd2253a16935ad9a99/completions/pyenv.zsh#L5

Haven't tested in bash, not sure if bash pyenv works fine

closed time in a day

hanxiao

issue commentpyenv/pyenv

`compctl` does not fallback to filename completion

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

hanxiao

comment created time in a day

created repositoryashfurrow/task-list-checker

created time in a day

PR opened pyenv/pyenv

Add 3.10.0b3

This simply copies and updates the 3.10.0b2 recipe.

Make sure you have checked all steps below.

Prerequisite

  • [ ] Please consider implementing the feature as a hook script or plugin as a first step.
    • pyenv has some powerful support for plugins and hook scripts. Please refer to Authoring plugins for details and try to implement it as a plugin if possible.
  • [ ] Please consider contributing the patch upstream to rbenv, since we have borrowed most of the code from that project.
    • We occasionally import the changes from rbenv. In general, you can expect changes made in rbenv will be imported to pyenv too, eventually.
    • Generally speaking, we prefer not to make changes in the core in order to keep compatibility with rbenv.
  • [ ] My PR addresses the following pyenv issue (if any)
    • Closes https://github.com/pyenv/pyenv/issues/XXXX

Description

  • [ ] Here are some details about my PR

Tests

  • [ ] My PR adds the following unit tests (if any)
+10 -0

0 comment

1 changed file

pr created time in 2 days

PR opened pyenv/pyenv

#1813 fix broken feature.

Make sure you have checked all steps below.

Prerequisite

  • [ ] Please consider implementing the feature as a hook script or plugin as a first step.
    • pyenv has some powerful support for plugins and hook scripts. Please refer to Authoring plugins for details and try to implement it as a plugin if possible.
  • [ ] Please consider contributing the patch upstream to rbenv, since we have borrowed most of the code from that project.
    • We occasionally import the changes from rbenv. In general, you can expect changes made in rbenv will be imported to pyenv too, eventually.
    • Generally speaking, we prefer not to make changes in the core in order to keep compatibility with rbenv.
  • [x] My PR addresses the following pyenv issue (if any)
    • Closes https://github.com/pyenv/pyenv/issues/1813

Description

  • [x] Here are some details about my PR I found the last working version is v1.2.22. here is compare: https://github.com/pyenv/pyenv/compare/v1.2.22..v2.0.1 Please note the differences in these files:
  • libexec/pyenv
  • libexec/pyenv-rehash

Tests

test-pyenv.py

#!/usr/bin/env python

import sys
print("Python version")
print (sys.version)

print("Version info.")
print (sys.version_info)
for ver in system 3.6.13 3.7.10 3.8.10 3.9.5
  echo "##### $ver #####"
  mkdir -p $ver
  cp test-pyenv.py $ver
  pushd $ver
  pyenv local $ver
  popd
  # run script out of directory
  $ver/test-pyenv.py
end

Result:

##### system #####
('script:', 'system/test-pyenv.py')
Python version
2.7.16 (default, May  8 2021, 11:48:02)
[GCC Apple LLVM 12.0.5 (clang-1205.0.19.59.6) [+internal-os, ptrauth-isa=deploy
Version info.
sys.version_info(major=2, minor=7, micro=16, releaselevel='final', serial=0)
##### 3.6.13 #####
script: 3.6.13/test-pyenv.py
Python version
3.6.13 (default, Jun 18 2021, 12:05:19)
[GCC Apple LLVM 12.0.5 (clang-1205.0.22.9)]
Version info.
sys.version_info(major=3, minor=6, micro=13, releaselevel='final', serial=0)
##### 3.7.10 #####
script: 3.7.10/test-pyenv.py
Python version
3.7.10 (default, Jun 18 2021, 17:34:04)
[Clang 12.0.5 (clang-1205.0.22.9)]
Version info.
sys.version_info(major=3, minor=7, micro=10, releaselevel='final', serial=0)
##### 3.8.10 #####
script: 3.8.10/test-pyenv.py
Python version
3.8.10 (default, Jun 18 2021, 17:28:52)
[Clang 12.0.5 (clang-1205.0.22.9)]
Version info.
sys.version_info(major=3, minor=8, micro=10, releaselevel='final', serial=0)
##### 3.9.5 #####
script: /Users/kzhang/Documents/workspaces/MyWorkspace/pyenv-tests/3.9.5/test-pyenv.py
Python version
3.9.5 (default, Jun 18 2021, 11:18:55)
[Clang 12.0.5 (clang-1205.0.22.9)]
Version info.
sys.version_info(major=3, minor=9, micro=5, releaselevel='final', serial=0)
+31 -0

0 comment

2 changed files

pr created time in 2 days

issue commentpyenv/pyenv

How to install pyenv system-wide

I wonder if for that case (wanting to create virtual environments that are not managed/co-located with pyenv) you would be better using virtualenv directly. I haven't had problems doing that:

  1. You set the pyenv version that you want the virtual environment (e.g., pyenv shell 3.6.3)
  2. Create the virtual environment virtualenv ~/venvs/my_venv_3.
  3. Load the environment source ~/venvs/my_venv_3/bin/activate

That will make python point to the pyenv version you used to create the environment, even if later you change the pyenv version.

Unfortunately I do want pyenv to manage my virtual environments for multiple users, but that's were some problems appear :)

albireox

comment created time in 2 days

issue commentpyenv/pyenv

How to install pyenv system-wide

Hi, I'm looking to do the same thing. Basically install pyenv in /opt/pyenv/, but then give each user the ability to create their own pyenv virtualenvs in their home directory. But this seems seems to want to use the PYENV_ROOT and seems klinda hard-coded, if I'm seeing correctly.

https://github.com/pyenv/pyenv-virtualenv/blob/294f64f76b6b7fbf1a22a4ebba7710faa75c21f7/bin/pyenv-virtualenv#L356

Effectively, I want to give users the ability to create virtualenvs based on pyenv-installed python versions. But I'm not able to have users privately install pyenv in their home directories, install and compile pyenv python versions in their home directories as well, and then create pyenv virtualenvs off of that. Instead, I'd like users to be able to create virtualenvs in their home directories, based on existing python versions installed in /opt/pyenv/.

Is this possible with pyenv?

albireox

comment created time in 2 days

issue commentpyenv/pyenv

pyenv global x.x.x not changing the python version

run the command 'pyenv init --path', paste the output in your shell (~/.zshrc) at the end line, to enable shims. and after that add 'eval "$(pyenv init -)" ' source ~/.zshrc

only this worked for me!

ghost

comment created time in 2 days

issue closedpyenv/pyenv

Not building fcntl module when using pyenv install

When using pyenv install, module fcntl is not been build. When using build from source it works perfectly.

Tested with pyenv 3.8.9 and 3.9.5 both works out of pyenv but do not work with pyenv.

hostname = linwell1 uname -m = x86_64 uname -r = 5.8.0-55-generic uname -s = Linux uname -v = #62~20.04.1-Ubuntu SMP Wed Jun 2 08:55:04 UTC 2021

Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.3.0-17ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) pyenv 2.0.1-5-gbbcecc75

Looking at logs seems that pyconfig.h for any reason is writing when some .h files are not found. #define HAVE_STROPTS_H 1 and this define is preventing fcntl to be build.

config.log

python-build.20210615141435.518951.log

closed time in 2 days

wellrats

issue commentpyenv/pyenv

Not building fcntl module when using pyenv install

There was a stropts.h in /usr/include with no content. File removed. pyenv install sucessfully done with fcntl. Sorry guys, closing the case.

wellrats

comment created time in 2 days

issue commentpyenv/pyenv

Provide shims for micro/patch releases (python3.7.4)

Welp, I didn't mean to.

I would expect to need to reference the version in a pyenv global call

I don't really follow how the third segment of the version is so utterly silly to want while the second segment is regular normal functionality for pyenv.

altendky

comment created time in 2 days

issue closedpyenv/pyenv

Not able to install python 3.6 with pyenv

Prerequisite

  • [x] Make sure your problem is not listed in the common build problems.
  • [x] Make sure no duplicated issue has already been reported in the pyenv issues. You should look for closed issues, too.
  • [x] Make sure you are not asking us to help solving your specific issue.
    • GitHub issues is opened mainly for development purposes. If you want to ask someone to help solving your problem, go to some community site like Gitter, StackOverflow, etc.
  • [x] Make sure your problem is not derived from packaging (e.g. Homebrew).
    • Please refer to the package documentation for the installation issues, etc.
  • [x] Make sure your problem is not derived from plugins.
    • This repository is maintaining pyenv and the default python-build plugin only. Please refrain from reporting issues of other plugins here.

Description

  • [x] Platform information: Manjaro Linux (Linux 5.10.41-1-MANJARO)
  • [x] OS architecture: x68_64
  • [x] pyenv version: 2.0.1
  • [x] Python version: 3.6.5
  • [x] C Compiler information: 11.1.0

Issue

Installed pyenv via pyenv-installer and tried to install python versions 3.6.5 with pyenv:

env PYENV_DEBUG=1 pyenv install -v 3.6.5

Also tried python versions 3.6.9, 3.6.11. None of them are working. Getting a similar output (partial) for all:

rm -f /home/psk/.pyenv/versions/3.6.5/bin/pyvenv
(cd /home/psk/.pyenv/versions/3.6.5/bin; ln -s pyvenv-3.6 pyvenv)
if test "x" != "x" ; then \
	rm -f /home/psk/.pyenv/versions/3.6.5/bin/python3-32; \
	(cd /home/psk/.pyenv/versions/3.6.5/bin; ln -s python3.6-32 python3-32) \
fi
rm -f /home/psk/.pyenv/versions/3.6.5/share/man/man1/python3.1
(cd /home/psk/.pyenv/versions/3.6.5/share/man/man1; ln -s python3.6.1 python3.1)
if test "xupgrade" != "xno"  ; then \
	case upgrade in \
		upgrade) ensurepip="--upgrade" ;; \
		install|*) ensurepip="" ;; \
	esac; \
	 ./python -E -m ensurepip \
		$ensurepip --root=/ ; \
fi
make: *** [Makefile:1099: install] Error 139
+++(/home/psk/.pyenv/plugins/python-build/bin/python-build:797): build_package_standard_install(): build_failed

+++(/home/psk/.pyenv/plugins/python-build/bin/python-build:126): build_failed(): echo
+++(/home/psk/.pyenv/plugins/python-build/bin/python-build:127): build_failed(): colorize 1 'BUILD FAILED'
+++(/home/psk/.pyenv/plugins/python-build/bin/python-build:91): colorize(): '[' -t 1 ']'
BUILD FAILED+++(/home/psk/.pyenv/plugins/python-build/bin/python-build:91): colorize(): printf '\e[%sm%s\e[m' 1 'BUILD FAILED'
++++(/home/psk/.pyenv/plugins/python-build/bin/python-build:128): build_failed(): os_information
++++(/home/psk/.pyenv/plugins/python-build/bin/python-build:97): os_information(): type -p lsb_release
++++(/home/psk/.pyenv/plugins/python-build/bin/python-build:98): os_information(): lsb_release -sir

Was able to install version 3.7+ without issue.

Note: there is a similar issue here (python2.7 on Arch Linux) but I couldn't fix this based on solutions for common build problems.

closed time in 3 days

pskrunner14

issue commentpyenv/pyenv

Not able to install python 3.6 with pyenv

@mitchhentges the patch fixed things for me! Thanks

pskrunner14

comment created time in 3 days

issue commentpyenv/pyenv

Not able to install python 3.6 with pyenv

Update: my issue is the same as #1889, and that could be the case here, too.

pskrunner14

comment created time in 3 days

issue commentpyenv/pyenv

Not able to install python 3.6 with pyenv

Hey, I'm encountering the exact same issue!

  • Platform information: Fedora 34
  • OS architecture: x86_64
  • pyenv version: 2.0.1
  • Python version: 3.9.5 (Host), 3.6.13 (attempted installation in pyenv)
  • C Compiler information: GCC 11.1.1 20210531 (Red Hat 11.1.1-3)
  • Verbose build log: https://gist.github.com/mitchhentges/c888168cca47333ee190bcfeb0ad45bd
pskrunner14

comment created time in 3 days

issue openedflask-restful/flask-restful

will flask restful be supported in fastapi? fast_restful?

We really like flask_restful and are now experimenting with fastapi. Do you have plans to make a similar integration in fast? https://github.com/tiangolo/fastapi

created time in 3 days

issue commentpyenv/pyenv

Python build fails on M1 Apple Silicon with arm64 homebrew

Can we please lock this closed issue? 70 comments is more than enough. Solutions to user issues should be in docs, not issues.

rjmoggach

comment created time in 4 days

issue commentpyenv/pyenv

Python build fails on M1 Apple Silicon with arm64 homebrew

All you need to do is installing brew for x64 and run pyenv in x64 as well:

arch -x86_64 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
eval "$(/usr/local/bin/brew shellenv)"
arch -x86_64 pyenv install 2.7.18

You will end up with two homebrew installations, the x64 version in /usr/local and the native m1 on /opt/homebrew, if by any reason you need to run the x64 version you just need to prepend arch -x86_64 to the command

rjmoggach

comment created time in 4 days

issue closedpyenv/pyenv

pyenv install failed. configure: error: cannot run C compiled programs

Too many issues will kill our team's development velocity, drastically. Make sure you have checked all steps below.

Prerequisite

  • [x] Make sure your problem is not listed in the common build problems.
  • [x] Make sure no duplicated issue has already been reported in the pyenv issues. You should look for closed issues, too.
  • [x] Make sure you are not asking us to help solving your specific issue.
    • GitHub issues is opened mainly for development purposes. If you want to ask someone to help solving your problem, go to some community site like Gitter, StackOverflow, etc.
  • [x] Make sure your problem is not derived from packaging (e.g. Homebrew).
    • Please refer to the package documentation for the installation issues, etc.
  • [x] Make sure your problem is not derived from plugins.
    • This repository is maintaining pyenv and the default python-build plugin only. Please refrain from reporting issues of other plugins here.

Description

  • [x] Platform information (e.g. Ubuntu Linux 16.04): macOS Big Sur 11.2.3
  • [x] OS architecture (e.g. amd64): Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64
  • [x] pyenv version: 1.2.27
  • [x] Python version: 3.9.2
  • [x] C Compiler information (e.g. gcc 7.3): 12.0.5
  • [x] Please attach verbose build log as gist
    • You can turn on verbose debug logging using by setting PYENV_DEBUG=1, e.g. env PYENV_DEBUG=1 pyenv install -v 3.6.4 https://gist.github.com/tsonglew/dfb82c468092d9abd9eefcaa84d615fd

closed time in 4 days

tsonglew

issue commentpyenv/pyenv

pyenv install failed. configure: error: cannot run C compiled programs

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

tsonglew

comment created time in 4 days

release flask-api/flask-api

v3.0

released time in 4 days

created repositorytjdevries/test_repo_plz_ignore

please ignore, do not star. IT WILL MESS UP MY TESTS!

created time in 4 days