Created attachment 323422 [details] build log If you try to build jinja with USE=doc, the following error occurs: sphinx-build -b html -d _build/doctrees . _build/html Traceback (most recent call last): File "/usr/bin/sphinx-build-2.7", line 9, in <module> load_entry_point('Sphinx==1.1.2', 'console_scripts', 'sphinx-build')() File "/usr/lib64/python2.7/site-packages/sphinx/__init__.py", line 47, in main from sphinx import cmdline File "/usr/lib64/python2.7/site-packages/sphinx/cmdline.py", line 22, in <module> from sphinx.application import Sphinx File "/usr/lib64/python2.7/site-packages/sphinx/application.py", line 26, in <module> from sphinx.roles import XRefRole File "/usr/lib64/python2.7/site-packages/sphinx/roles.py", line 20, in <module> from sphinx.util import ws_re File "/usr/lib64/python2.7/site-packages/sphinx/util/__init__.py", line 27, in <module> import jinja2 File "/var/tmp/portage/dev-python/jinja-2.6/work/Jinja2-2.6/build-3.2/lib.linux-x86_64-3.2/jinja2/__init__.py", line 33, in <module> from jinja2.environment import Environment, Template File "/var/tmp/portage/dev-python/jinja-2.6/work/Jinja2-2.6/build-3.2/lib.linux-x86_64-3.2/jinja2/environment.py", line 13, in <module> from jinja2 import nodes File "/var/tmp/portage/dev-python/jinja-2.6/work/Jinja2-2.6/build-3.2/lib.linux-x86_64-3.2/jinja2/nodes.py", line 106 class Node(object, metaclass=NodeType): ^ SyntaxError: invalid syntax Apparently, sphinx (using python-2) tries to load python3 code.
Created attachment 323424 [details] emerge --info
Suggested solution: bump sphinx dependency to 1.1.3-r3 and keyword it. With sphinx-1.1.3-r3 build completes fine.
Created attachment 323426 [details, diff] suggested fix
Can you try to re-install sphinx-1.1.2 and try it again?
(In reply to comment #4) > Can you try to re-install sphinx-1.1.2 and try it again? Same error. Tree timestamp: Tue Oct 2 08:39:40 UTC 2012
(In reply to comment #5) > (In reply to comment #4) > > Can you try to re-install sphinx-1.1.2 and try it again? > > Same error. Tree timestamp: Tue Oct 2 08:39:40 UTC 2012 Hitting the same thing, and it's making for annoyance for pkgcore/snakeoil fixes. Here's one thing that's fairly whacked- if you invoked python3.2 `which sphinx-build`, it forces python2.7. Additionally, if you check the deps of sphinx... it's =dev-lang/python-2*, despite py3k usage there. Those deps need to be fixed. Triggered it with 1.1.3-r2; issue still exists...
(In reply to comment #6) > Here's one thing that's fairly whacked- if you invoked python3.2 `which > sphinx-build`, it forces python2.7. /usr/bin/sphinx-build is a wrapper script that is looking at your currently eselected python. It will also obey EPYTHON if you have that set in the environment (per python.eclass). There's not really a nice way to make multi-abi support work without a wrapper. > Additionally, if you check the deps of sphinx... it's =dev-lang/python-2*, > despite py3k usage there. Those deps need to be fixed. I have updated the dependency in 1.1.3-r3, thanks.
hmm. Is this a chink in the armory? Available Python interpreters: [1] python2.5 [1] python2.5 [2] python2.6 * OR [2] python2.6 [3] python2.7 [3] python2.7 * jinja # USE=doc ebuild jinja-2.6.ebuild clean install yields Traceback (most recent call last): File "/usr/bin/sphinx-build-3.1", line 5, in <module> from pkg_resources import load_entry_point File "/usr/lib64/python3.1/site-packages/pkg_resources.py", line 2809, in <module> working_set.require(__requires__) File "/usr/lib64/python3.1/site-packages/pkg_resources.py", line 691, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib64/python3.1/site-packages/pkg_resources.py", line 589, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: docutils>=0.7 make: *** [html] Error 1 Still can fail. Seems the python 3.1 sphinx-build isn't up to the job. Available Python interpreters: [1] python2.5 [2] python2.6 [3] python2.7 [4] python3.1 [5] python3.2 * yields running install_scripts >>> Completed installing jinja-2.6 into /mnt/gen2/TmpDir/portage/dev-python/jinja-2.6/image/ builds fine. Is my understanding correct that $(PYTHON -f --ABI) is pulling the final of the listed ABIs? Any eselect python other 3.2 and it pulls 3.1 which it seems has incompatibilities. Simply substitute $(PYTHON -f --ABI) with a hard coded python3.2?
sphinx-1.1.2 is no longer in portage suggesting resolution OBSOLETE/WONTFIX
fixed by version bump.
