portage correctly downgrades when installing sphinx but after the fact an emerge -uDN @world can update docutils back to 0.18 and thus brakin any merge ops that include sphinx. Reproducible: Always Steps to Reproduce: 1. allow dev-python/docutils-0.18 onto system 2. build any application requiring sphinx or just run /usr/bin/sphinx-build --version 3. rip sphinx Actual Results: Traceback
Created attachment 751156 [details] output of '/usr/bin/sphinx-build --version'
A world upgrade should _not_ allow docutils to be upgraded because Sphinx should depend on an older version. We need more informatino, I think.
I did not check the ebuild to see if there was a restriction prior to filing. As this is likely a local issue, I will close in favor of realtime support options. Appologies around.