importing manim should not trigger `pygments.styles.get_all_styles` about manim HOT 4 OPEN

There appears to be some weird interaction between pygments (which manim uses in order to highlight code visualized via the Code mobject) and voltron, a package that we do not depend on in any way (your pip list output is gigantic!). The immediate workaround on your end would be to create a separate virtual environment and use manim from there:

$ python3.11 -m venv py-manim
$ source py-manim/bin/activate
$ pip install manim
$ manim -pql ...

However, I do see an issue with manim itself here too: we should probably avoid running pygments.styles.get_all_styles() on import manim, as this forces pygments to run a bunch of code that could probably be delayed to the point where Code is actually instantiated.

from manim.

There appears to be some weird interaction between pygments (which manim uses in order to highlight code visualized via the Code mobject) and voltron, a package that we do not depend on in any way (your pip list output is gigantic!). The immediate workaround on your end would be to create a separate virtual environment and use manim from there:

$ python3.11 -m venv py-manim
$ source py-manim/bin/activate
$ pip install manim
$ manim -pql ...

However, I do see an issue with manim itself here too: we should probably avoid running pygments.styles.get_all_styles() on import manim, as this forces pygments to run a bunch of code that could probably be delayed to the point where Code is actually instantiated.

Thanks. Creating a separate environment works for me.

I'm not going to close this issue because there's still an issue with manim itself. If it is required please feel free to help me close this issue.

from manim.

No, this issue should be left open; I've just updated title and description with more explicit tasks -- this is actually also a good issue for a first contribution to the library.

from manim.

Regarding the attribute removal, would it be a good idea, instead, to add a class method (say get_styles_list or something similar) that more or less accomplishes the same thing, but has the added benefit that it won't run during import. The reason being, it's a bit odd to specifically point someone to another library for a list of available code styles, especially if it's not as widely known as some. This class method would really just be a wrapper, but it might be a bit more cohesive.

from manim.