On Sat, 2017-01-28 at 18:40 +0000, Martin Gansser wrote:
thanks for your feedback, i run this from the doc dir of python-kivi
[martin@fc25 doc]$ PYTHONPATH=.. python autobuild.py silenced=yes
[INFO ] [Logger ] Record log in
/home/martin/.kivy/logs/kivy_17-01-28_5.txt
[INFO ] [Kivy ] v1.9.1
[INFO ] [Python ] v2.7.13 (default, Jan 12 2017, 17:59:37)
[GCC 6.3.1 20161221 (Red Hat 6.3.1-1)]
Traceback (most recent call last):
File "autobuild.py", line 25, in <module>
import kivy.app
File "/home/martin/rpmbuild/BUILD/kivy-1.9.1/kivy/app.py", line
319, in <module>
from kivy.base import runTouchApp, stopTouchApp
File "/home/martin/rpmbuild/BUILD/kivy-1.9.1/kivy/base.py", line
30, in <module>
from kivy.event import EventDispatcher
File "/home/martin/rpmbuild/BUILD/kivy-1.9.1/kivy/event.py", line
8, in <module>
import kivy._event
ImportError: No module named _event
kivi._event needs to be built with Cython, which means you need to
build the module before building the doc.
If you look at the Makefile at the root of the sources, it uses the
following to build the module:
python setup.py build_ext --inplace
This makes the built files go into the kivi/ folder, instead of the
build/ folder. That's what makes the module available for the docs to
build correctly.
But you probably don't want to build with --inplace, so use this to
build the docs:
cd doc && make html PYTHONPATH=../build/lib.linux-x86_64-2.7
You'll need to adapt the architecture and Python version of course.
--
Mathieu