6 posts tagged with "pyenv"

If your poetry install command is failing specifically when trying to install multidict (or packages that depend on it, like aiohttp or discord.py), the root cause is almost always a failure to compile the optional C extensions for the package.

Since multidict offers pre-compiled binaries (wheels) for standard Python versions on common operating systems, a compilation error indicates one of two things: the wheel is unavailable for your specific setup, or the local build tools are missing. Your use of pyenv often exacerbates the issue by complicating the environment setup.

The pyenv: python: command not found error occurs when pyenv is not properly configured to manage your Python versions. The solution is to ensure your shell's configuration files are correctly updated to point to pyenv's shims, which are small executable files that intercept commands like python and pip and redirect them to the correct Python version [4, 5].

You can switch Python versions with pyenv using three main commands: global, local, and shell. The method you choose depends on the scope you want for the new Python version.

Choosing the right Python environment and package management tool in 2025 depends on your project's complexity and your team's workflow. The tools available can be categorized into two main groups: those that manage Python versions (pyenv, asdf) and those that manage project dependencies (venv, virtualenv, Poetry). Combining these tools is often the most effective approach.

Homebrew is the recommended and easiest way to install pyenv on macOS, but you can install it without Homebrew by cloning the repository from GitHub. This method requires a few extra steps, including manually configuring your shell and installing dependencies.