-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
[BUG] Install issue on Python3.12: Conflicting Dependencies #376
Comments
Hello @Wizorx, thank you for reporting this issue! Maybe PyOpenGL is not available on Python 3.12, or on Windows. Did you try not installing Anyway, Python 3.12 is not well-supported, because of #293. I highly recommend installing Python 3.11 if you can :-) |
That worked perfectly, thank you! |
You're welcome! |
What solution did you use above? |
I used the |
Hello @Wizorx, I think this SO answer could probably help you: https://stackoverflow.com/a/77364602. Can you try this out and tell me if that solve your issue? Of course, one of the solutions is to downgrade to Python 3.11. |
Sorry for the delayed response, but it seems virutalenv won't run properly, when I try to run any commands, my cmd responds with something along the lines of "virtualenv is not an recognized command". I guess I'm better off downgrading to python 3.11. The thing is: how do I do that? |
On Windows, Linux or macOS, you need to make sure the commands are listed in one of the directories listed in the environment variable By default, this is very likely that the program installed with Python's pip are not placed in a directory that is listed in Also, depending on your OS (Windows, Ubuntu, macOS, ...), the name of the Python executable can be different. For example, on Windows, Python is not If you have multiple Python 3.x versions installed, you can use Then,
Actually, there is no easy way for downgrading Python. You can just install another Python version on your computer. If you do not need Python 3.12 anymore, I suggest you to first uninstall it. Then, install Python 3.11 from the official website: https://www.python.org/downloads/. |
Ok, so it seemed I had both 3.12 and 3.11 installed. I uninstalled both and reinstalled 3.11 just to be sure, but then it broke manimce. VSCode won't recognize it, choco won't uninstall it, nor will it force a reinstall. I deleted all files and folders related to choco, scoop and pip, removed their references in PATH and tried to install them all again, along with python 3.11, but no dice. What can I do now? edit: when trying to install manimce through choco, i get this at the very end `
|
I am sorry to hear that you have troubles installing Manim and Manim Slides :/ Could you share the full error trace back? There should be important information in it. Regardless, I recommend you post you question on Manim’s Reddit, Discord or GitHub issues :-) |
Ok, for some reason when I ran choco install manimce without installing python first, it worked, but with two issues, first one is that manim slides, for some reason, uses manim 0.17.3 while the version I have installed is 0.18.0, which I don't understand. The second one is I've manage to render the Example scene successfully but I couldn't render a file I had lying around. I got this output for my file:
|
Hey @Wizorx, sorry for the delay! The above error is likely caused by outdated slides, that were generated with an old version of Manim Slides. When using The easiest would be to delete the |
Closing, as this should be solved now (thanks to work on #465). |
Please explain the issue you're experiencing (with as much detail as possible):
Hello everyone! I've been using manim-slides for quite some time now but recently I changed PCs and when I tried to install manim-slides on the new one I just couldn't. Pipx seems to be working fine, as does manim. But When I try do install manim-slides, I get this error: "Cannot install manim-slides because these package versions have conflicting dependencies." I'm on Windows 11 using Python 3.12. Any help is welcome, thanks in advance!
The text was updated successfully, but these errors were encountered: