Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommend pipx for MacOS users #3775

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JasonGrace2282
Copy link
Contributor

Closes #3656

Taking inspiration from the homebrew docs, I changed the installation instructions for macOS to use pipx. For most users, this should be enough.

@JasonGrace2282 JasonGrace2282 added the documentation Improvements or additions to documentation label May 21, 2024
Copy link
Member

@behackl behackl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll test this later today! I've used pipx before to make binaries available (which would help the manim-binary in our case too), but I've never tried to interact with the environments created by pipx (e.g., in order to add more packages, or to use it with an IDE).

Installing additional packages to the same pipx-managed venv as manim is then located in is possible via pipx inject manim package_name, and IDEs could probably be made happy too if we documented that the manim-venv is located at ~/.local/pipx/....

If everything works smoothly like that, I'm fine with recommending pipx. Otherwise, if the interaction with the pipx-managed environment is awkward, I'd probably rather recommend creating a plain venv instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: 🆕 New
2 participants