Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #82386

Kivy Wheel Download

Newsgroups comp.lang.javascript
Date 2023-12-30 19:21 -0800
Message-ID <fb0bae0b-e1b4-4e35-9da8-0bd257469422n@googlegroups.com> (permalink)
Subject Kivy Wheel Download
From Barbie Plecker <pleckerbarbie@gmail.com>

Show all headers | View raw


Activate the virtual environment. You will have to do this step from the current directoryevery time you start a new terminal. This sets up the environment so the new kivy_venvPython is used.



kivy wheel download

Download https://t.co/UKlFp7q7tP 






If a wheel is not available or is not working, Kivy can be installed from sourcewith some additional steps. Installing from source means that Kivy will be installedfrom source code and compiled directly on your system.


Instead, we recommend installing the SDL dependencies from source. This is the same processour CI uses to build the wheels. The SDL dependencies are built from source and installed into aspecific directory.


The script will download and build the SDL dependencies from source. It will also installthe dependencies into a directory named kivy-dependencies. This directory will be usedby Kivy to build and install Kivy from source with SDL support.


Kivy will need to know where the SDL dependencies are installed. To do so, you must setthe KIVY_DEPS_ROOT environment variable to the path of the kivy-dependencies directory.For example, if you are in the kivy-deps-build directory, you can set the environmentvariable with:


This creates a kivy named folder in your current path. Next, follow the same steps of theInstalling from source above, but instead of installing Kivy via adistribution package or zip file, install it as aneditable install.


The following selectors install backends packaged as wheels by kivy under the Kivy_deps namespace.They are typically released and versioned to match specific Kivy versions, so we provide selectorsto facilitate installation (i.e. instead of having to do pip install kivy kivy_deps.sdl2==x.y.z,you can now do pip install "kivy[sdl2]" to automatically install the correct sdl2 for the Kivyversion).






kivy_deps.gstreamer is an optional dependency which is only needed for audio/video support.We only provide it on Windows, for other platforms it must be installed independently.Alternatively, use ffpyplayer instead.


One can select which of these to use for OpenGL using theKIVY_GL_BACKEND environment variable: By setting it to glew(the default), angle_sdl2, or sdl2. Here, angle_sdl2 is a substitute forglew but requires kivy_deps.sdl2 be installed as well.


To execute any of the pip or wheel commands given here, you need a command line (here also called console, terminal, shell or bash, where the last two refer to Linux / *BSD Unix style command lines) and Python must be on the PATH.


As opposed to the last stable release (which we discussed in the previous section), nightlywheels contain all the latest changes to Kivy, including experimental fixes.For installation instructions, see Pre-release, pre-compiled wheels.


We also provide nightly wheels generated using Kivymaster. See Nightly wheel installation.See also Upgrading from a previous Kivy dist. If installing kivy to an alternatelocation and not to site-packages, please see Installing Kivy to an alternate location.


Know your command line. To execute any of the pipor wheel commands, one needs a command line tool with python on the path.The default command line on Windows isCommand Prompt, and thequickest way to open it is to press Win+R on your keyboard, type cmdin the window that opens, and then press enter.


To achieve using Kivy in an alternate location extra tweaking is required.Due to this issue wheel andpip install the dependency wheels to python\Lib\site-packages\kivy. Sothey need to be moved to your actual kivy installation from site-packages.


To install the new wheels to a previous Kivy distribution all the files andfolders, except for the python folder should be deleted from the distribution.This python folder will then be treated as a normal system installed python andall the steps described in Installation can then be continued.


I got this error while "Preparing wheel metadata" and "Building wheel for Kivy (PEP 517)" as well. I think that it is worth mentioning that every time I said that error occurred, it occurred twice, one after another.


I understand Kivy ships with a color picker (kivy.uix.colorpicker), which is great and all, but I just want the wheel - the color wheel. That's all I want to have show in a certain space. The entire other half of the layout I don't need. At all.


Using kivy's KV, ColorWheel as a widget shows absolutely nothing, but doesn't throw any errors. I'm really confused because it seems as though the wheel itself is a pretty standalone widget (looking at the documentation) and I have no idea why I can't see it.


If you correctly setup your path variables as I explained in the previous section then this should execute a pip package download. Once this is done, you are almost ready to be able to use the Python wheel packages.


You could use a command line, but I kept running into a memory error issue maybe due to it being a large file (121 MB) and my firewall and anti-virus program so I just went to the PyPI site to download the wheel. I downloaded the appropriate version for my Python 2.7, 32-bit. ( kivy.deps.gstreamer-0.1.12-cp27-cp27m-win32.whl). Once the file is downloaded to our usual location, run pip install:


note: This error originates from a subprocess, and is likely not a problem with pip.

ERROR: Failed building wheel for cryptography

Failed to build cryptography

ERROR: Could not build wheels for cryptography, which is required to install pyproject.toml-based projects


Wheels are precompiled binaries for all linux platforms using the manylinux2010 tag.In the following, replace python with python3 for Python 3.To install first update pip (at least pip v19.0 is required to support a manylinux2010 wheel):


cairo: Standard flag, let kivy use cairo graphical libraries.camera: Install libraries needed to support camera.doc: Standard flag, will make you build the documentation locally.examples: Standard flag, will give you kivy examples programs.garden: Install garden tool to manage user maintained widgets.gstreamer: Standard flag, kivy will be able to use audio/video streaming libraries.spell: Standard flag, provide enchant to use spelling in kivy apps.


build is a simple tool which can among other things buildwheels for projects using PEP 517. It is comparable to the execution of pip wheel --no-deps ..It can also build source distributions which is not possible with pip.pip wheel covers the wheel scope of build but offers many additional features.


Fortunately for me, I don't need to worry about all that complexity in thewider ecosystem when I'm specifically wearing my contextlib2 maintainerhat - I just publish an sdist and a universal wheel file to PyPI, and the restof the ecosystem has everything it needs to take care of redistributionand end user consumption without any further input from me.


However, contextlib2 is a pure Python project that only depends on thestandard library, so it's pretty much the simplest possible case from atooling perspective (the only reason I needed to upgrade from distutils tosetuptools was so I could publish my own wheel files, and the only reason Ihaven't switched to using the much simpler pure-Python-only flit instead ofeither of them is that that doesn't yet easily support publishing backwardscompatible setup.py based sdists).


Between the wheel format and the manylinux1 usefully-distro-independentABI definition, this is largely handled now, with conda available as anoption to handle the relatively small number of cases that are still a problemfor pip.


While redistributors will generally take care of converting upstream Pythonpackages into their own preferred formats, the Python-specific wheel formatis currently a case where it is left up to publishers to decide whether ornot to create them, and if they do decide to create them, how to automate thatprocess.


Thus, it currently makes sense to defer this cost to individual projects, asthere are quite a few commercial continuous integration and continuousdeployment service providers willing to offer free accounts to open sourceprojects, and these can also be used for the task of producing releaseartifacts. Projects also remain free to only publish source artifacts, relyingon pip's implicit wheel creation and caching and the appropriate use ofprivate PyPI mirrors and caches to meet the needs of end users.


For downstream platform communities already offering shared buildinfrastructure to their members (such as Linux distributions and conda-forge),it may make sense to offer Python wheel generation as a supported output optionfor cross-platform development use cases, in addition to the platform's nativebinary packaging format.


To install, download the wheel and install with a command such as pip install -4.29-py3-none-any.whl or pip install ./pgadmin4-4.29-py3-none-any.whl if you've manually downloaded the file. It is strongly recommended that a Python Virtual Environment is used.


Why?Most Linux distributions use the GNU version (glibc) of the standard C library that is required by pretty much every C program, including Python.But Alpine Linux uses musl, those binary wheels are compiled against glibc, and therefore Alpine disabled Linux wheel support.


An update: PEP 656 and related infrastructure mean pip and PyPI now support wheels for the musl C library, and therefore for Alpine.Build tools like cibuildwheel have started adding support, so Alpine-compatible wheels will start becoming more widely available.Semi-official wheels for NumPy, Scipy and the like can be found here; they might eventually make it to PyPI.


Then we install the required toolchain and dependencies necessary for bothns-3 (e.g. libxml2, gsl, sqlite, gtk, etc) and for the bindings and packaging(e.g. setuptools, wheel, auditwheel, cmake-build-extension, cppyy).


Auditwheel needs to be called resolve and copy external librariesthat we need to ship along the ns-3 module libraries (e.g. libxml2, sqlite3,gtk, gsl, etc). However, we need to prevent auditwheel from shipping copies ofthe libraries built by the ns-3 project. A list of excluded libraries is generatedby the script ns-3-dev/build-support/pip-wheel/auditwheel-exclude-list.py.

 35fe9a5643


Back to comp.lang.javascript | Previous | Next | Find similar | Unroll thread


Thread

Kivy Wheel Download Barbie Plecker <pleckerbarbie@gmail.com> - 2023-12-30 19:21 -0800

csiph-web