So does anyone have any objections or issues with this?
On Tue, Oct 18, 2016 at 8:14 PM, Todd Rme firstname.lastname@example.org wrote:
Currently the primary python-specific way to package compiled Python modules is the "wheel" format , which is basically a zip file containing the compiled module with some metadata describing it.
Normally, openSUSE disallows using pre-compiled packages. This typically isn't a problem, since python packages are also usually distributed as sources, either in .tar.gz, .zip, or some other similar format, and contain a script (usually setup.py) to build the module.
However, some very simple packages, specifically those built using the flit tool , only provide wheels. They don't provide any script to install the package, they can only be built from source if flit is already present. However, in those cases, the wheel is composed only of uncompiled python script files (.py files) and metadata.
It would conceivably be possible to use flit to build these packages from, for example, github tarballs. However, flit has some serious bootstrapping issues (it depends on packages built using flit), is difficult to install, and it is difficult to get useful files for packaging out of it.
So for packages that don't come with their own build script, and whose wheels lack any compiled code, I think it should be allowed to use the wheel for packaging our rpms.
What does everyone else think?
1: https://www.python.org/dev/peps/pep-0491/ 2: https://pypi.python.org/pypi/flit