Publish pip-installable Python bindings

[ncoghlan]

This is less an issue-to-be-resolved and more an FYI regarding the previously unclaimed solv name on PyPI: I've started a pypi-solv project at https://github.com/ncoghlan/pypi-solv with the aim of producing a pip-installable sdist and a manylinux1 wheel file for libsolv's Python bindings.

Right now, that's just a placeholder module that does nothing more than emit a runtime warning when imported: https://pypi.org/project/solv/0.0.1/

Longer term, I'm aiming to make it default to providing a standalone statically linked version of the extension module: ncoghlan/pypi-solv#1

[ignatenkobrain]

Seems that pypi-solv repo is archived now and I don't think there is much benefit of publishing bindings to PyPI from upstream project. So closing.

[crazyscientist]

Actually, I kind of find it weird, if projects decide against publishing their Python packages via PyPi. Python's dependency management is quite comfortable, but every time a package is not available one has to tell other people: "Please don't forget to also install that".

[dralley]

@ncoghlan @ignatenkobrain

I spent a few hours working on getting libsolv packageable as a Python package, as I have with createrepo_c and libcomps, because it's useful to the Pulp project to be able to use Python packages instead of RPMs for CI/CD, upstream source installations, etc.

If you would be receptive to merging that work, (once I am done) I can clean it up and make a PR. We'll probably use those packages even if they aren't on PyPI or if the patch doesn't end up merged upstream because it simplifies everything for our workflow. But it would be nice if it could benefit more than just us.

re: the description of https://pypi.org/project/solv/, I am using scikit-build (cmake integration for setuptools), which predates pep517 and supporting it is still an open issue. Not sure how much that matters.

[dralley]

I now have something that seems to be functional, though obviously not mergable yet and I haven't thoroughly tested it.

master...dralley:python-package

[dralley]

@ncoghlan I got a CI set up to automatically build platform-independent wheels: https://github.com/dralley/libsolv/runs/447432218?check_suite_focus=true#step:7:228

Are you still interested in this package? If not, and if libsolv upstream is also not interested, would you consider giving access to https://pypi.org/user/pulp/?

[dralley]

@ignatenkobrain @mlschroe

I've released the first real libsolv packages to PyPI: https://pypi.org/project/solv/#history

If it's something the upstream project might now be interested in, I can clean up the patch into something mergable, and also give you ownership of the PyPI namespace if you so desire. Otherwise, we will just maintain the Python package ourselves.