MetaSIP - a GUI Development Tool for SIP
SIP is a Python bindings generator for C and
C++ libraries. It takes as its input a set of .sip text files that describes
the history of the API of the library. A .sip file is similar to a C/C++
header file but with addional directives, annotations and supplementary
hand-written C/C++ code.
MetaSIP (specifically the msip application) is a GUI tool for specifying the
complete history of a library's API allowing additional directives, annotations
and hand-written code to be added. A .msp project file is used to store this
information and MetaSIP (specifically the msipgen application) can generate
an appropriate set of .sip files to feed to SIP.
The key feature of MetaSIP is that it can scan the header files of a particular version of a library in order to initially populate the project file. It will then indicate all of the tasks that might need to be performed in order to complete the implementation of the bindings. It will also scan a new version of the library, compare it with the previous version, update the project file appropriately, and indicate any new tasks that now might need to be performed in order to keep the bindings up to date. These features make it relatively easy to maintain the bindings for a large library.
Currently the scanning of a library's header files is done using CastXML and this must also be installed.
MetaSIP is implemented with Python and PyQt6.
It should be noted that MetaSIP was developed a number of years ago by the author as a personal productivity tool. As a result it is fairly feature complete. However because it has not been used by a significant number of people, its behavour may seem quirky in places. It is certainly poorly documented with no online help.
Documentation
The documentation can be found at Read the Docs.
License
MetaSIP is licensed under the BSD 2 clause license.
Installation
To install msipgen, run:
pip install metasip
To install the additional dependencies required by the msip GUI development
tool, run:
pip install 'metasip[gui]'
Creating Packages for Distribution
Python sdists and wheels can be created with any standard Python build frontend.
For example, using build an sdist and wheel will be created from a checkout in the current directory by running:
python -m build --outdir .
Building the Documentation
The documentation is built using Sphinx, myst_parser and the sphinx-rtd-theme theme.
Change to the docs directory of a checkout and run:
make html
The HTML documentation can then be found in the _build/html subdirectory.
Metadata
Release files for metasip 2.16.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| metasip-2.16.0.tar.gz | 84.5 kB | Without provenance | Details for metasip-2.16.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| metasip-2.16.0-py3-none-any.whl | Python 3 | none | any | Details for metasip-2.16.0-py3-none-any.whl |
Total release size: 240.8 kB
Release files / metasip-2.16.0.tar.gz
| Download URL | metasip-2.16.0.tar.gz |
|---|---|
| Size | 84.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82ea105afe8ebe30c18d24d435772b194ef75f2245642ca378269836b9a0d6f4
|
|
BLAKE2b-256 checksum How to use checksums |
9f399f4e0a34b8b0ae934331a6ada8797f77fc5b49752f617e7fe83c93e91ee3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.0
|
Release files / metasip-2.16.0-py3-none-any.whl
| Download URL | metasip-2.16.0-py3-none-any.whl |
|---|---|
| Size | 156.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7f52a45367d8f9018518a04f8f9985098c5a93063dac0f965a67f59f8a9be00
|
|
BLAKE2b-256 checksum How to use checksums |
78ddd185dcb140837cc89a2b75a16cbd52efa1835f726851a23e7a1c272e48a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.0
|
Security for metasip 2.16.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.