[Bug 217447] textproc/py-sphinx: Fails with python:3.3+
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Mar 1 11:08:07 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217447
Bug ID: 217447
Summary: textproc/py-sphinx: Fails with python:3.3+
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: kmoore at FreeBSD.org
Reporter: dbaio at bsd.com.br
CC: freebsd-python at FreeBSD.org
Flags: maintainer-feedback?(kmoore at FreeBSD.org), exp-run?
Assignee: kmoore at FreeBSD.org
Created attachment 180389
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180389&action=edit
py-sphinx-python3-error.patch
To reproduce it just set python 3.5 as default and execute a poudriere
testport.
DEFAULT_VERSIONS+= python=3.5
$ poudriere testport ... -o textproc/py-sphinx
>cd /wrkdirs/usr/ports/textproc/py3-sphinx/work/Sphinx-1.4.8/build/lib &&
>/usr/bin/env PYTHONPATH=/wrkdirs/usr/ports/textproc/py3-sphinx/work/Sphinx-1.4.8/build/lib:/usr/local/lib/python3.5/site-packages
>/usr/local/bin/python3.5 -m sphinx.pycode.pgen2.driver -c 'import load_grammar'
>/usr/local/lib/python3.5/runpy.py:125: RuntimeWarning: 'sphinx.pycode.pgen2.driver' found in
>sys.modules after import of package 'sphinx.pycode.pgen2', but prior to execution of
>'sphinx.pycode.pgen2.driver'; this may result in unpredictable behaviour
> warn(RuntimeWarning(msg))
Removing post-build block fixes this.
This was introduced in ports r336515 version 1.2 and then on version 1.2.1
this caught my attention:
* #1152: Fix pycode parsing errors of Python 3 code by including two grammar
versions for Python 2 and 3, and loading the appropriate version for the
running Python version.
https://github.com/sphinx-doc/sphinx/blob/master/CHANGES#L1687-L1689
I did some tests with this attached patch and couldn't find any problem, but
another eye on it will be great... and maybe an exprun...
Regards.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list