Address current failing sphinx packages for development

[vmcj]

We do generate the docs already before so the virtualenv is not that problematic. I will investigate if we can do something else so we don't need this but for now this is the best we can do.

This does block releasing though (although this also exists in the older releases) as a dependency for us is broken.

Closes: #2199

[eldering]

We do generate the docs already before so the virtualenv is not that problematic. I will investigate if we can do something else so we don't need this but for now this is the best we can do.

This does block releasing though (although this also exists in the older releases) as a dependency for us is broken.

Closes: #2199

This explanation is confusing: we generate the doce before what? How does that make the virtualenv not that problematic?

Also, is #2205 an alternative for this PR?

[vmcj]

We do generate the docs already before so the virtualenv is not that problematic. I will investigate if we can do something else so we don't need this but for now this is the best we can do.
This does block releasing though (although this also exists in the older releases) as a dependency for us is broken.
Closes: #2199

This explanation is confusing: we generate the doce before what? How does that make the virtualenv not that problematic?

In a normal release I thought (I verified and we don't) we already package the team manual. In that case only the one running make dist would need the extra virtual environment.

Also, is #2205 an alternative for this PR?

Yes, I think we should merge the other one if we accept the difference in the manual, but documenting how people can run make dist when doing development is a cleaner fix for the original issue (it was also easier to make sure we do fix this, only later did I realize how to find the actual issue).

[vmcj]

So by making the manual ugly in the other PR mentioned above, the issue is now fixed so I'll close this one.