Dear Maintainer,
I used to install tensorflow with pip, and sphinx-build had no trouble
building my documentation which includes `import tensorflow`.
Since we are not supposed to use pip directly anymore, I created a
virtual environment, with the option --system-site-packages since I only
want to add a few things not packaged in Debian, and installed
tensorflow in it. I now activate the environment, run sphinx-build,
and... it fails to find tensorflow.
The issue is that sphinx-build starts with #!/usr/bin/python3 , it does
not use the python3 symlink that the activation added at the beginning
of PATH, and thus does not look for packages in my active virtual
environment.
I have many possible workarounds:
* execute python3 -m sphinx.cmd.build
* execute python3 /usr/bin/sphinx-build
* export a PYTHONPATH pointing to the virtual environment
* install another copy of sphinx in the virtual environment
etc
but they essentially mean that the sphinx-build script shipped by Debian
is useless to me, I just use the first workaround instead.
The most natural change would be to use #!/usr/bin/env python3, but
Debian policy says not to do that. Is there a way this policy could be
relaxed when there is a good reason? Or is there another way to let
sphinx-build do the right thing with virtual environments? Or should I
resign myself?