Page MenuHome

blender-2.90.0 fails to build documentation: Some types are not used: ['hair', 'pointcloud']
Needs Information from User, NormalPublic


System Information
Operating system: Gentoo Linux amd64
Graphics card: GeForce GTX 750

Blender Version
Broken: v2.90.0
Worked: v2.83.5

Short description of error
When building documentation for blender-2.90.0, following error happens:

Traceback (most recent call last):
  File "/tmp/portage/portage/media-gfx/blender-2.90.0/work/blender-2.90.0/doc/python_api/", line 2252, in <module>
  File "/tmp/portage/portage/media-gfx/blender-2.90.0/work/blender-2.90.0/doc/python_api/", line 2176, in main
  File "/tmp/portage/portage/media-gfx/blender-2.90.0/work/blender-2.90.0/doc/python_api/", line 2040, in rna2sphinx
  File "/tmp/portage/portage/media-gfx/blender-2.90.0/work/blender-2.90.0/doc/python_api/", line 1180, in pycontext2sphinx
    str([member for member in context_type_map if member not in unique]))
Exception: Some types are not used: ['hair', 'pointcloud']

Exact steps for others to reproduce the error

  1. build blender from sources

I've used following cmake build switches:

  1. generate documentation via call to doc/python_api/ or using commands cd doc/python_api ; sphinx-build sphinx-in BPY_API

Event Timeline

Aaron Carlisle (Blendify) changed the task status from Needs Triage to Needs Information from User.Fri, Sep 4, 2:38 AM

What version of the source did you use? using rBa96283ba511d7ebf2c2ec2db16815b5a4b2979df I had no issue.

I'm using sources from With there were no such issues for me.

I also was slightly incorrect in original post. It's not cd doc/python_api ; sphinx-build sphinx-in BPY_API commands which fail. It's one that goes before that:

BLENDER_SYSTEM_SCRIPTS="/tmp/portage/portage/media-gfx/blender-2.90.0/work/blender-2.90.0/release/scripts" BLENDER_SYSTEM_DATAFILES="/tmp/portage/portage/media-gfx/blender-2.90.0/work/blender-2.90.0/release/datafiles" /tmp/portage/portage/media-gfx/blender-2.90.0/work/blender-2.90.0_build/bin/blender --background --python doc/python_api/ -noaudio

where /tmp/portage/portage/media-gfx/blender-2.90.0/work/blender-2.90.0 is a source directory and /tmp/portage/portage/media-gfx/blender-2.90.0/work/blender-2.90.0_build is build directory.

If issue is not in blender sources, could it be related to versions of dependencies or some missing dependencies?

I'll try checking later if source from commit you mentioned builds fine for me.

Ok, I ran some tests. When I'm using commit a96283ba511d7ebf2c2ec2db16815b5a4b2979df (branch master), documentation builds fine. When I'm using branch blender-v2.90-release (either from tag v2.90.0 from git, commit 0330d1af29c067cf309e4798f5259e01a8c3c668, which is also at the moment the latest commit in that branch,, or from tarball I'm getting error described in first message.

You need to make sure you are running the same version of Blender to generate the docs. You might have a particular build configuration that disables ['hair', 'pointcloud']

I'm using same version of Blender to generate the docs. I'm building blender and using it to generate docs. Yes, I might have configuration which has disabled hair and pointcloud stuff, but this configuration is same as one used for 2.83.5 and earlier blender versions. All enabled stuff and some disabled stuff should be listed in first message. What is required to enable hair and pointcloud? Did requirements change from 2.83.5? And are they different in master branch and commit a96283ba511d7ebf2c2ec2db16815b5a4b2979df ?

I have a same issue.

I used blender 2.90.0 (i.e. and tag v2.90.0.
Instead, it works correctly when I used windows version (
I think commit 83e3d25bcae37df0139bb93b85d7ae5bf3da553b is the cause of this issue which disabled hair and pointcloud by default.

So, the error condition in doc/python_api/ should be fixed to consider the various build options.
What do you think?

Looks like you found relevant commit causing this issue for me. I agree that adding similar conditions to doc/python_api/ should help.

nutti (Nutti) added a comment.EditedMon, Sep 7, 7:09 AM

I could generate .rst document by omitting L1031 and L1408 in doc/python_api/ which is introduced by the commit 83e3d25bcae37df0139bb93b85d7ae5bf3da553b.
I think we should fix this more elegant way, but this workaround works for the document generation.