Re: ImportError: No module named kivy, when run make html

2017-01-29 Thread Mathieu Bridon
On Sun, 2017-01-29 at 09:51 +, Martin Gansser wrote:
> thanks for your answer.
> 
> my question is, should i build for both python version the html files
> ?
> cd doc && make html PYTHONPATH=../build/lib.linux-%{_arch}-
> %{python2_version}
> cd ..
> cd doc && make html PYTHONPATH=../build/lib.linux-%{_arch}-
> %{python3_version}

Up to you.

Is the documentation going to be different between the python2-kivy and
python3-kivy package?

If yes, then having both python2-kivy-doc and python3-kivy-doc makes
sense.

Otherwise, just build it once as python-kivy-doc (bonus points if you
make it noarch) with whichever version of Python (although python3
being the default now, that's probably the one to use).

There's no need to do more work than necessary.


-- 
Mathieu
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: ImportError: No module named kivy, when run make html

2017-01-29 Thread Martin Gansser
thanks for your answer.

my question is, should i build for both python version the html files ?
cd doc && make html PYTHONPATH=../build/lib.linux-%{_arch}-%{python2_version}
cd ..
cd doc && make html PYTHONPATH=../build/lib.linux-%{_arch}-%{python3_version}
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: ImportError: No module named kivy, when run make html

2017-01-28 Thread Mathieu Bridon
On Sat, 2017-01-28 at 18:40 +, 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 
>  import kivy.app
>    File "/home/martin/rpmbuild/BUILD/kivy-1.9.1/kivy/app.py", line
> 319, in 
>  from kivy.base import runTouchApp, stopTouchApp
>    File "/home/martin/rpmbuild/BUILD/kivy-1.9.1/kivy/base.py", line
> 30, in 
>  from kivy.event import EventDispatcher
>    File "/home/martin/rpmbuild/BUILD/kivy-1.9.1/kivy/event.py", line
> 8, in 
>  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
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: ImportError: No module named kivy, when run make html

2017-01-28 Thread Martin Ueding
The _event module seems to be a Cython and not a regular Python module.
I would assume that you have to compile the main program before you can
use it. Another possibility would be that `python` is the wrong Python
interpreter and another one (`python3` or perhaps something that can
handle `.pyx` and `.pxd` files).
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: ImportError: No module named kivy, when run make html

2017-01-28 Thread Martin Gansser
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 
 import kivy.app
   File "/home/martin/rpmbuild/BUILD/kivy-1.9.1/kivy/app.py", line 319, in 

 from kivy.base import runTouchApp, stopTouchApp
   File "/home/martin/rpmbuild/BUILD/kivy-1.9.1/kivy/base.py", line 30, in 

 from kivy.event import EventDispatcher
   File "/home/martin/rpmbuild/BUILD/kivy-1.9.1/kivy/event.py", line 8, in 

 import kivy._event
 ImportError: No module named _event
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: ImportError: No module named kivy, when run make html

2017-01-28 Thread Martin Ueding
Am 28.01.2017 um 18:16 schrieb Martin Gansser:
> ImportError: No module named kivy

It tries to import the kivy module (itself), but that is not available
in the `doc` directory. So either call the `autobuild.py` from the root
(such that the `kivy` directory is there, or call it with

PYTHONPATH=.. python autobuild.py silenced=yes

from the `doc` directory such that it picks up the files from there.

Another way would be to have a separate documentation package that would
have `python-kivy` as a `BuildRequires` and could use the already
compiled version. However that would mean two discrete packages.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


ImportError: No module named kivy, when run make html

2017-01-28 Thread Martin Gansser
I am working on a review https://bugzilla.redhat.com/show_bug.cgi?id=1416705
and the build of the documentation fails with the following error message:

+ cd doc
+ make html
mkdir -p build/html build/doctrees
python autobuild.py silenced=yes
Traceback (most recent call last):
  File "autobuild.py", line 22, in 
import kivy
ImportError: No module named kivy
Makefile:80: recipe for target 'html' failed
make: *** [html] Error 1
+ exit 0

how can i resolve this ?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org