I have a set of rst files that I am building in readthedocs with sphinx. The files have multiple bullet lists, but they are not being rendered correctly.
The text appears, but there are no bullet symbols or nesting / indentation.
To make sure it was not my files, I did a direct copy-paste from the sphinx_rtd_theme page (https://github.com/readthedocs/sphinx_rtd_theme/blob/b07560bf97dad3a4266f6145bd4b662ac708ab00/docs/demo/lists_tables.rst)
This is what the rst is supposed to render as (with ::marker for each list item in the html file)
This is what I am getting when I build the same rst using my local sphinx / rtd setup
Is there something I need to fix in my conf.py or other files?
We had the same issue (bullet points disappearing in lists) after refreshing the conda environment we use for releasing one of our packages. The other solutions listed here (thus far) didn't work for me, but downgrading docutils <0.17 did.
We are using nbsphinx (some of our docs illustrate operations with notebooks), and had recently some issues due to related package versions (jinja2, sphinx, docutils). Based on issues/comments (such as this one and that one), we used various older versions of these packages.
But as of this writing and thanks to the hard work of all the maintainers, we were able to remove all pins except for docutils. FWIW, for our current needs, the relevant subset of packages we use is:
docutils 0.16 py38_1
jinja2 3.0.0 pyhd3eb1b0_0
nbsphinx 0.8.6 pyhd8ed1ab_1 conda-forge
sphinx 4.0.1 pyhd3eb1b0_0
sphinx_rtd_theme 0.4.3 py_0
I had the same issue when using Read-The-Docs as a theme along with Sphinx-AutoAPI. Based on the answer of "Pierre D" I downgraded the docutils using:
conda install docutils=0.16
The solution worked for me. Both, missing bullets and the elongated line spacings were resolved. I guess the problem is caused by a bug in the docutils package and hope it will be fixed soon.
Other answers here point to docutils as the having the bug. But, the bug is actually in sphinx-rtd-theme. So, even though downgrading docutils seems to work, the solution that worked for us, that I think is better, is to
upgrade sphinx and sphinx-rtd-theme past the bugfix. For us, that looked like requiring sphinx>=4.3.0 and sphinx-rtd-theme>=0.5.1 (see our PR)
Seems to be a issue with sphinx_rtd_theme and new HTML5 tags in docutils. See https://github.com/readthedocs/sphinx_rtd_theme/issues/1115 for more info. As mentioned, current resolution is downgrade to docutils=0.16.
I just discovered that an RtD documentation set I maintain was experiencing this exact problem, where bullets would show on my local builds (accompanied by the ::marker in the page source) but would be absent in RtD builds (no ::marker in the page source).
I tried a couple of things that didn't work before finding this thread. Nick Crews's answer worked perfectly: I added the >=0.5.1 lower-bound constraint to the requirements-rtd.txt file that I've configured RtD to use (I already had a Sphinx==5.3.0 pin, for reasons), and poof! I had my bullets back.
UPDATE 31 Jan 2023: Based on the comments in this sphinx_rtd_theme GitHub issue, it's also important to be sure that the version of docutils that gets installed is not too high. The thread recommends a constraint of docutils<0.17, though in recent builds my bullets have rendered fine with docutils==0.17.1.
This got me curious as to why it was necessary for me to add this constraint, when I'd already had sphinx-rtd-theme declared in requirements-rtd.txt.
On taking a closer look at my RtD build logs, I discovered that RtD has its own default-requirements install step, prior to installing anything I specify in my config. In this default install step, it was installing sphinx-rtd-theme<5.0:
Collecting sphinx-rtd-theme<0.5
Downloading sphinx_rtd_theme-0.4.3-py2.py3-none-any.whl (6.4 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.4/6.4 MB 117.0 MB/s eta 0:00:00
Thus, when pip hit the sphinx-rtd-theme line in requirements-rtd.txt, it just ignored it, because a version of it was already installed:
Successfully installed attrs-22.1.0 importlib-metadata-5.0.0 sphinx-5.3.0
sphinx-issues-3.0.1 sphinx-removed-in-0.2.1 sphinxcontrib-applehelp-1.0.2
sphinxcontrib-devhelp-1.0.2 sphinxcontrib-htmlhelp-2.0.0 sphinxcontrib-jsmath-1.0.1
sphinxcontrib-programoutput-0.17 sphinxcontrib-qthelp-1.0.3 zipp-3.10.0
Adding the >=0.5.1 constraint thus forces an upgrade/reinstall of sphinx-rtd-theme to the latest version, fixing the problem.
So... where did this sphinx-rtd-theme<0.5 pin come from?
After digging into the RtD source for a while, I found out that there's a toggle for, essentially, "are we using the latest Sphinx version or not?":
# If defaulting to Sphinx 2+, we need to push the latest theme
# release as well. `<0.5.0` is not compatible with Sphinx 2+
self.project.get_feature_value(
Feature.USE_SPHINX_LATEST,
positive='sphinx-rtd-theme',
negative='sphinx-rtd-theme<0.5',
),
So, okaaay... I do want to use a recent version of Sphinx... why am I apparently set up to not USE_SPHINX_LATEST?
Looks like it's a compatibility decision made at some point. Any RtD docset created before a certain date (20 Oct 2020, for a personal project like mine; or, 21 Jan 2021 for RtD for Business projects) is set as not USE_SPHINX_LATEST. I assume these dates were picked for some strategic reason, likely having to do with in-the-wild usage of Sphinx < 2.0 dropping below some threshold.
Anyways! If you see a sphinx-rtd-theme<0.5 and/or sphinx<2 constraint in your RtD build logs, that's why. And, again, follow Nick Crews's advice to fix it.
I had the same problem, when listing using *, in the .rst file like:
* first item
* second item
I found out that the problem, in my case, was that I was using the theme sphinx_rtd_theme, but I didn't add it in extensions in the conf.py file. So adding the following worked for me:
extensions = [sphinx_rtd_theme,
# other extensions
]
Creating a new sphinx project solved the problem
Had the same problem:
Creating new sphinx-quickstart didn't work.
Reducing docutils to 0.16 and adding 'sphinx_rtd_theme' to the extensions list in conf.py worked:
extensions = ['sphinx_rtd_theme']
My goal is to visualize a point cloud using PCL. This is possible according to their official tutorial (link). In the tutorial there is an include path pointing to cloud_viewer.h file (located under visualization folder). After a vcpkg install using "vcpkg install pcl:x64-windows" I couldn’t find the visualization folder. After some research it I found out that "visualization" does not come with default PCL install, but it is an optional feature (link). Then I used the "vcpkg install pcl[vtk]:x64-windows --featurepackages" and I am still missing the needed folder. If anyone could point out to me where am I making a mistake I would appreciate it.
I got the same problem with you. It seems vcpkg is not a good choice for pcl library. Many people have the same problem with visualization module
Using vcpkg does not provide all files, includes and headers for pcl.
I had the same issue, and downloading pcl all in one solved it.
You can find it here for example: http://unanancyowen.com/en/pcl181/
Other thing that can help, is to use this command on vcpkg:
.\vcpkg install pcl:x64-windows-static
I tried running the code:
library optmum, pgraph; optset; graphset;
and obviously it says I need to install the packages and all but I am not sure where exactly I am supposed to go to find these. I went to the Install application and package manager but neither seems to have the packages I am looking for. Ideally, I would like to have these packages in my library and run the command above. How do i proceed with this Gauss software?
pgraph comes standard with GAUSS, so you only need the optmum library. It is listed with the name of "op" and description of "Optmization 3.1".
If you don't own it, it will show up with a light red background to indicate that you don't own the package.
I want to draw 3D PCA with pylot (Scatter3d), however the graphics is not showing up in jupyterlab only in jupyter-notebook.
I've installed the 'jupyterlab_plotly' package and I was able to create an 'jupyterlab_plotly.Plotly object', but I couldn't figure out how to actually include/draw the graphics in the notebook.
I wonder if someone could post a working example of drawing figures in jupyterlab with pyplot.
(The example at the project's git site - https://github.com/gnestor/jupyterlab_plotly- only present an 'jupyterlab_plotly.Plotly object', but not the graphics itself)
Thanks,
I had the same issue. Looks like the project has moved over here:
https://github.com/jupyterlab/jupyter-renderers
Installing with the suggested:
jupyter labextension install #jupyterlab/plotly-extension
worked for me.
This is now superseded by jupyter labextension install jupyterlab-plotly as per https://plotly.com/python/getting-started/#jupyterlab-support-python-35
The answer by #user1561393 describes a good solution.
I want to add that the plotly documentation also covers these steps in some extra detail in their 'Getting started' guide. This should normally remain up-to date even when some they migrate to newer services (as has happened with their V4).
I am getting a No such module Toaster. I have installed the pod, also after searching on SO, I fixed the red Pod_Project.Framework issue. Now its gray. I also verified Framework Search Path's and ensured that the Pod in question is recursive.
I have read thru this and this. Ideally I expected that things should have worked by default, just install the Pod and import and it should work. Is this expectation incorrect ? Should I need to change settings everytime I install a pod ?
EDIT 1
Also added Toaster pod to the Framework Search Path
Still the same No such module error on the import.
EDIT 2
I tried opening the .xcworkspace. But same issue again.
#siddharth as you mention above is correct. But Linked FrameWorks and Libraries are not in build Settings. It is In Build Phases