How to correctly setup Kivy in a Repl.it
I was testing things out ... and I've found that under certain conditions ... Kivy works in a Pygame repl. https://repl.it/@Saibot84/Kivy-code-snippets
Step 1: Run the following python code
(In that repl, this code is saved as setup.txt We can copy it from there to main.py to run it)
Run the kivy code (but wait for kivy's wheels to be built, which take a while)
My question is ... how can we make sure that Cython and Cython.Distutils are built first ... before kivy gets built?
- I tried using requirements.txt to require Cython and kivy ... kivy's build was throwing an error that it couldn't find Cython.Distutils
- I tried creating a polygott repl ... and in run, having it pip install cython, then pip install kivy ... but pip was downloading the packages from the internet ... and the downloads were freezing/crashing the polygott repl container.
- In the python code, I tried importing subprocess and using subprocess.call to "pip install cython" ... but this was also downloading from the internet and crashing the polygott repl container.
- If the python code includes the line "import kivy" ... Repl is auto-installing the package ... even if I try calling subprocess to pip install cython /before/ the import kivy line of code is ever reached.
I know the Pygame and the polygott repls aren't "meant" for kivy ... but kivy is able to run.
Does anyone know how to control that cython and cython.distutils be built before kivy is built?
Edit 2020-01-04 - replaced "virtual polygott computer" with "polygott repl container"
I've recently come back to this ... and after some experimentation ...
Here's a polygott repl that installs kivy from a local wheelhouse, then runs the x11 vnc server and then the python code.
It will seem to hang while installing Kivy ... but you can check the nohup.out file to see the installation progress until the server and code are started. (By the way, it seems that sending output to nohup prevents the repl from crashing.)
Here's a Python3 with Pygame repl ... that uses a requirements.txt file to install kivy. Running it looks like it hangs while building Kivy, but just wait for it to finish.
Here's a polygott repl that has kivy preinstalled ... so the build runs much faster. It, too, then runs the x11 vnc server and then the python code.
I've recently come back to the Polygott-Kivy-PreInstalled and found that it was broken / it wouldn't run /or it would crash when loading. So I've rebuilt it ... now using a setup.py script to handle installing kivy, and it only installs kivy it if it's not already installed.
When Kivy and Kivy-Garden gets built by pip3, it creates wheels in the
/home/runner/.cache/pip/ subdirectories. Copying those wheels into the wheelhouse directory has now successfully bypassed/saved the whole build process and the repl should run almost immediately every time.
Edit: Other key ingredients for this were:
pip3 download -d ./wheelhouse package_name_hereto download the wheels locally
pip3 install --no-index --find-links=./wheelhouse/ kivyto install using the local wheels
The polygott container used by Polygott-Kivy-PreInstalled is now using python 3.8 ... which is not supported by Kivy 1.11.1 and this is preventing the repl from running. I'm working on finding an alternative solution for polygott.
In the meantime, here is a Python3.8 repl (including a local copy of Kivy 2.0.0rc3) that can run the Kivy showcase Kivy-Showcase-Python38-PreInstalled
Backing up the wheels isn't necessary either if we use
Kivy = "^2.0.0rc3" in
pyproject.toml together with
[tool.poetry.dev-dependencies.Kivy] url = "https://kivy.org/downloads/ci/linux/kivy/Kivy-2.0.0rc3-cp38-cp38-manylinux2010_x86_64.whl"
as seen here: Python38-Kivy-200rc3
Update 2020-08-27: Polygott repls are unable to show graphics. Even a simple X application fails to work. Polygott Simple Xclock Test
Great question @Alt_Plus_F4 !
Here's an example of Pyglet running in a Polygott REPL.
By using a polygott repl, we can controlling the installation using a Makefile.
For for a faster time-to-interactive I have:
- downloaded the wheels for
- and after building the future package once, I moved the wheel file into the local directory
- then listed the two wheel files in
- and used
pip3 install -r requirements.txtto install the packages from the local directory
I hope that helps.