Description
Too many issues will kill our team's development velocity, drastically.
Make sure you have checked all steps below.
Prerequisite
- Make sure your problem is not listed in the common build problems.
- Make sure no duplicated issue has already been reported in the pyenv-virtualenv issues. You should look in closed issues, too.
- 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.
- Make sure your problem is not derived from packaging (e.g. Homebrew).
- Please refer to the package documentation for the installation issues, etc.
- Make sure your problem is not derived from other plugins.
- This repository is maintaining the
pyenv-virtualenv
plugin only. Please refrain from reporting issues of other plugins here.
- This repository is maintaining the
Description
- Platform information (e.g. Ubuntu Linux 20.04): macOS 15.0 Sequoia
- OS architecture (e.g. amd64): amd64 (MacbookPro 14,3)
- pyenv version: v2.4.13
- pyenv-virtualenv version: v1.2.4
- Python version: 3.12.6
- virtualenv version (if installed): none
I was using pyenv
& pyenv-virtualenv
on macOS 12.x Monterey for 2 years with great success.
Yesterday, I updated to macOS 15.0 Sequoia (clean install).
The shell was very slow with pyenv-virtualenv
autoloading enabled.
It takes around 1.2 seconds when hitting a blank line in the shell.
I downgraded to macOS 13.x Ventura (clean install again) and the shell was instant again.
I don't expect you to fix macOS, but I wanted to report my experience with Sequoia to see if others users have the same problem. Apart from pyenv-virtualenv
, pyenv
+ jenv
+ rbenv
were also a bit slower. The rest of the apps were working well. I suspect Apple to have changed something with the terminal / shell...
I'll stick to Ventura for sometimes, and I'll give a try to Sonoma to see.