Skip to content

Commit a309894

Browse files
authored
Merge branch 'main' into refactor-tests
2 parents ee19a49 + e648d88 commit a309894

File tree

1 file changed

+20
-20
lines changed

1 file changed

+20
-20
lines changed

docs/source/installation/troubleshooting.rst

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,15 @@ Troubleshooting
44
Version incompatibility
55
***********************
66

7-
Confusion and conflict between versions is by far the most common reason
8-
for installation failures. Some signs and errors resulting from this are
9-
as follows:
7+
Confusion and conflict between versions are by far the most common reasons
8+
for installation failures. Some errors resulting from this are:
109

1110
- ``There are no scenes in that module``
1211
- ``ModuleNotFoundError: No module named 'manim'``
1312
- ``ModuleNotFoundError: No module named 'manimlib'``
13+
14+
Some reasons that conflict may occur are:
15+
1416
- You followed any tutorial created before October 2020 (because the community edition did not exist before then)
1517
- You cloned a repository on GitHub (installation of the community version for normal use does not require the cloning of any repository)
1618
- Different import statements (explained below)
@@ -65,15 +67,15 @@ them with:
6567
pip uninstall <package>
6668
6769
68-
If you have cloned a repository from GitHub, you should either remove it
70+
If you cloned manim from GitHub, you should either remove it
6971
or run manim outside that folder.
7072

7173
Other errors
7274
************
7375

7476
``pip install manim`` fails when installing manimpango?
7577
-------------------------------------------------------
76-
Most likely this means that pip was not able to use our pre-built wheels
78+
This most likely means that pip was not able to use our pre-built wheels
7779
of ``manimpango``. Let us know (via our `Discord <https://www.manim.community/discord/>`_
7880
or by opening a
7981
`new issue on GitHub <https://github.com/ManimCommunity/ManimPango/issues/new>`_)
@@ -87,19 +89,19 @@ instructions given in
8789
of the corresponding `GitHub repository <https://github.com/ManimCommunity/ManimPango>`_.
8890

8991

90-
(Windows) OSError: dlopen() failed to load a library: pango?
91-
------------------------------------------------------------
92+
(Windows) OSError: dlopen() failed to load a library: pango
93+
-----------------------------------------------------------
9294

9395
This should be fixed in Manim's latest version, update
9496
using ``pip install --upgrade manim``.
9597

9698

9799

98-
Some letters are missing from Text/Tex output?
99-
------------------------------------------------------------
100+
Some letters are missing from Text/Tex output
101+
---------------------------------------------
100102

101103
If you have recently installed TeX you may need to build the fonts it
102-
uses. Which can be done by running:
104+
uses. This can be done by running:
103105

104106
.. code-block:: bash
105107
@@ -108,8 +110,8 @@ uses. Which can be done by running:
108110
109111
.. _dvisvgm-troubleshoot:
110112

111-
Installation does not support converting PDF to SVG?
112-
----------------------------------------------------
113+
Installation does not support converting PDF to SVG
114+
---------------------------------------------------
113115

114116
First, make sure your ``dvisvgm`` version is at least 2.4:
115117

@@ -148,7 +150,7 @@ If, however, ``--libgs=filename`` appears in the help, that means that your
148150
``/opt/local/lib``). Please look carefully, as the file might be located
149151
elsewhere, e.g. in the directory where Ghostscript is installed.
150152

151-
As soon as you have found the library, try (on Mac OS or Linux)
153+
When you have found the library, try (on Mac OS or Linux)
152154

153155
.. code-block:: bash
154156
@@ -173,7 +175,7 @@ As a last check, you can run
173175
174176
dvisvgm -V1
175177
176-
while still having ``LIBGS`` set to the correct path, of course. If ``dvisvgm``
178+
(while still having ``LIBGS`` set to the correct path, of course.) If ``dvisvgm``
177179
can find your Ghostscript installation, it will be shown in the output together
178180
with the version number.
179181

@@ -193,7 +195,7 @@ Follow the steps in `this StackExchange answer <https://superuser.com/questions/
193195
--------------------------------
194196

195197
If ``choco install manimce`` failed,
196-
it is likely being caused by Python not being added to your ``PATH`` variable properly.
198+
it is likely because Python was not added to your ``PATH`` variable properly.
197199
Try running the following commands in your terminal:
198200

199201
1. ``py --version``
@@ -206,18 +208,16 @@ If none of these commands are recognized,
206208
this means that Python was installed on your system, but was not added to PATH.
207209
See above for directions to add it to your PATH variable.
208210

209-
If any of these commands opens up the Windows store,
211+
If any of these commands open the Windows store,
210212
this is likely interfering with the process.
211-
This is because Chocolatey runs a command that calls python or python3,
212-
and opening up the Windows store is not the expected behavior.
213213
See below to fix aliases.
214214

215215
(Windows) Fix Aliases
216216
---------------------
217217

218218
1. Go to the Windows Settings.
219-
2. Under Apps and Features, there are an application execution aliases.
220-
3. Within this menu disable the alias(es) that is causing the issue (``python`` and/or ``python3``).
219+
2. Under Apps and Features, there are application execution aliases.
220+
3. Within this menu disable the alias(es) that are causing the issue (``python`` and/or ``python3``).
221221

222222
``IndexError: List index out of range``
223223
---------------------------------------

0 commit comments

Comments
 (0)