-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libbtrfsutil python bindings not available in pip #310
Comments
Yes, that sounds great, thanks. I'm not familiar with pypi packaging, so please let me explore that first, but that you did the test build test will sure help. |
Did this go anywhere? I've been working with BTRFS and want to use a venv without having to resort to site-packages. |
Not yet, sorry. |
OK - I'll try to figure out what @niklasfi did, see if I can build my own. |
I would also be interested in having this available in PyPi, is there an option to raise a PR for this and include it, as suggested by @niklasfi, in the CI build to be published? |
So, it's there, https://pypi.org/project/btrfsutil/ . Manual upload, got some problems with python packaging and generated files.
I'd appreciate some feedback what else is missing or what should be fixed (and how). I'm not sure about versioning, currently it's 6.10 but there are almost no changes to the python code. Should the python package be versioned separately or in lockstep with whole project despite producing many no-change versions? |
Fixes so 'python3 -m build' works and package can be uploaded to pypi (https://pypi.org/project/btrfsutil/). - setup.py is still used for local build (make) - for pypi it must be done by 'python3 -m build' that is build in a temporary directory - btrfsutilpy.h must be also distributed - version is set manually (the git VERSION file is not accessible) - the project page metadata is empty, the README.md should be added Issue: #310 Signed-off-by: David Sterba <[email protected]>
Fixes so 'python3 -m build' works and package can be uploaded to pypi (https://pypi.org/project/btrfsutil/). - setup.py is still used for local build (make) - for pypi it must be done by 'python3 -m build' that is build in a temporary directory - btrfsutilpy.h must be also distributed - version is set manually (the git VERSION file is not accessible) - the project page metadata is empty, the README.md should be added Issue: #310 Signed-off-by: David Sterba <[email protected]>
Note that after these changes |
Ah right, thanks. I need to update the release checklist. |
@kdave just a gentle reminder since 6.11 was still released with 6.10: |
Thanks, 6.11 published. |
[ ci skip ] Issue: #310 Signed-off-by: David Sterba <[email protected]>
Provide at least basic description of the library for pypi.org main page. It's for libbtrfsutil that mentions the C and python usage. [ ci skip ] Issue: #310 Signed-off-by: David Sterba <[email protected]>
This mostly reverts the commit 8f1f2e7 ("libbtrfsutil: update btrfsutil long description"). There is no need to introduce such a drama to create a temporary pypi-README.md, just reuse the existing one in libbtrfsutil/README.md. This does not only make the code simpler, but pass CI. Issue: kdave#310 Fixes: 8f1f2e7 ("libbtrfsutil: update btrfsutil long description") Signed-off-by: Qu Wenruo <[email protected]>
This mostly reverts the commit 8f1f2e7 ("libbtrfsutil: update btrfsutil long description"). There is no need to introduce such a drama to create a temporary pypi-README.md, just reuse the existing one in libbtrfsutil/README.md. This does not only make the code simpler, but pass CI. Issue: kdave#310 Fixes: 8f1f2e7 ("libbtrfsutil: update btrfsutil long description") Signed-off-by: Qu Wenruo <[email protected]>
This mostly reverts the commit 8f1f2e7 ("libbtrfsutil: update btrfsutil long description"). There is no need to introduce such a drama to create a temporary pypi-README.md, just reuse the existing one in libbtrfsutil/README.md. This does not only make the code simpler, but pass CI. Issue: kdave#310 Fixes: 8f1f2e7 ("libbtrfsutil: update btrfsutil long description") Signed-off-by: Qu Wenruo <[email protected]>
…escription Instead of copying the file during custom build commands, just use a soft link to re-use the existing README.d from libbtrfsutil. Issue: kdave#310 Signed-off-by: Qu Wenruo <[email protected]>
…escription Instead of copying the file during custom build commands, just use a soft link to re-use the existing README.d from libbtrfsutil. Issue: kdave#310 Signed-off-by: Qu Wenruo <[email protected]>
…escription Instead of copying the file during custom build commands, just use a soft link to re-use the existing README.d from libbtrfsutil. Issue: kdave#310 Signed-off-by: Qu Wenruo <[email protected]>
…escription Instead of copying the file during custom build commands, just use a soft link to re-use the existing README.d from libbtrfsutil. Issue: kdave#310 Signed-off-by: Qu Wenruo <[email protected]>
…escription Instead of copying the file during custom build commands, just use a soft link to re-use the existing README.d from libbtrfsutil. Issue: #310 Signed-off-by: Qu Wenruo <[email protected]>
The python bindings located in libbtrfsutil/python are not available within the pypi repository. This makes it very complicated for programmers to use them.
Since most of the work is already done (
setup.py
is included in the repository), it was not that difficult for me to create and upload a pipy package to the testing server using the following Dockerfile:The result is available on the pypi testing server.
Is the btrfs-progs project interested in adding python package creation to its ci pipelines? If so, how can I help integrating it?
The text was updated successfully, but these errors were encountered: