|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|The hacker's browser.|
|bind.js - simple two way data binding to HTML and callbacks|
|Bindgen||152||2 years ago||26||gpl-3.0||Crystal|
|Binding and wrapper generator for C/C++ libraries|
|Moya Modelmapper||134||38||4 years ago||27||February 18, 2020||6||mit||Swift|
|ModelMapper bindings for Moya.|
|Lychee||115||7 months ago||1||May 27, 2021||15||apache-2.0||Kotlin|
|The most complete and powerful data-binding library and persistence infra for Kotlin 1.5, Android & Splitties Views DSL, JavaFX & TornadoFX, JSON, JDBC & SQLite, HTTP, SharedPreferences.|
|Umbel||89||7 years ago||1|
|UMBEL (Upper Mapping and Binding Exchange Layer) has two purposes. Its first purpose is to provide a general vocabulary (the UMBEL "vocabulary") of classes and predicates for describing domain ontologies, with the specific aim of promoting interoperability with external datasets and domains. The second purpose is to provide a coherent framework of broad subjects and topics (the UMBEL "reference concepts"), suitable as binding nodes for mapping relevant Web-accessible content, also with the specific aim of promoting interoperability and to reason over a coherent reference structure and its linked resources. UMBEL presently has about 28,000 of these reference concepts drawn from the Cyc knowledge base, which are organized into more than 30 mostly disjoint SuperTypes.|
|Pyparted||84||40||2||24 days ago||8||March 31, 2022||11||gpl-2.0||C|
|Python bindings for GNU parted (libparted)|
|Vim Macrobatics||71||a year ago||5||mit||Vim script|
|Plugin for Vim that makes it easier to record / play / edit macros|
|Lunatik Ng||59||8 years ago||1||C|
|Linux Kernel Lua Scripting Engine|
|Adds vim bindings to nodejs readline.|
pyparted is a set of native Python bindings for libparted. libparted is the library portion of the GNU parted project. With pyparted, you can write applications that interact with disk partition tables and filesystems.
The Python bindings are implemented in two layers. Since libparted itself is written in C without any real implementation of objects, a simple 1:1 mapping of externally accessible libparted functions was written. This mapping is provided in the _ped Python module. You can use that module if you want to, but it's really just meant for the larger parted module.
|_ped||libparted Python bindings, direct 1:1: function mapping|
|parted||Native Python code building on _ped, complete with classes, exceptions, and advanced functionality.|
The _ped module is written and maintained by hand. I chose to do this rather than rely on a tool like SWIG or Pyrex for several reasons. Mostly because I was the GNU parted maintainer, but also because libparted is sort of complex. It's a lowlevel system tool and I found it doesn't translate well in the tools I tried. This is nothing against those tools, I just don't think libparted is ideal to go through SWIG or Pyrex. By writing my own bindings, I can also find bugs in libparted that I may have overlooked before. See the WHY file for more explanation as to why I wrote the bindings by hand.
pyparted started life at Red Hat and continues there today. The main reason for writing it was to let anaconda (the Red Hat installation program, now used by RHEL and Fedora and many other distributions) interact with libparted. Anaconda is written in Python, so native bindings made sense.
pyparted went through many rewrites, but the end result was always the same. And incomplete API via Python with just enough provided for anaconda to do its job.
The latest iteration of pyparted aims to be a complete API mapping and even provide a nice set of classes so that people might want to integrate it in to other installers or even write other applications (maybe a Python based alternative to parted(8) or fdisk(8)).
Example code is provided in the examples directory. These may help provide a gentle introduction to the usage concepts of pyparted. More examples are always welcome, as are improved explanatory commentary for those that exist.
If you are reporting a pyparted failure in Fedora, it's most useful if you file a bug at http://bugzilla.redhat.com/ against the appropriate Fedora release you are using.
Alternatively, you can file bugs directly on the project page: https://github.com/dcantrell/pyparted/issues
If you just have questions about pyparted, you can email us directly using the contact information in the AUTHORS file. We will do our best to help you.