This release is a pre-release and may not be stable for production use.
======
CFFIpp is like [cffi](https://cffi.readthedocs.org), but
generates bindings for C++, by mapping them to C through cffi.
License
=======
CFFIpp is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
CFFIpp is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with CFFIpp. If not, see <http://www.gnu.org/licenses/>.
Example
=======
Comes straight from a unit test:
```python
ffi = FFIpp()
ffi.cdef("""
class testClass {
public:
testClass();
void test(int);
int returnsInt(int);
private:
void shouldNotBeInModule();
};
""")
self.assertTrue(ffi.has_class("testClass"))
ffi.set_source("example_module", """
class testClass {
public:
testClass(){}
void test(int){/*nop*/}
int returnsInt(int){return 1;}
private:
void shouldNotBeInModule() {/*nop*/}
};""")
ffi.compile()
import example_module
c = example_module.testClass()
self.assertEqual(c.returnsInt(5), 1)
```
Caveats
=======
1. This is experimental software;
2. Adds a (albeit tiny) layer between Python and your C++ classes,
using a stupid C wrapper.
3. No overloading support, no type conversion yet, except for the `cffi`
stuff.
4. Returning C++ objects from methods will not yield Python objects yet.
5. Will only wrap classes, not mixable with C stuff at this moment.
6. Ironically, you probably need CPython to run this, because it relies on
clang bindings to proprocess C++ code.
Development
===========
Development takes place at [my GitLab repository](https://gitlab.com/rubdos/cffipp/).
Merge requests and issues are welcome. If you want to start hacking on this project,
feel free to do so. Good starting places are the TODO.md file and the caveats listed before.
Metadata
Release files for CFFIpp 0.1.0.dev2
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 |
|---|---|---|---|---|
| CFFIpp-0.1.0.dev2.tar.gz | 4.8 kB | Without provenance | Details for CFFIpp-0.1.0.dev2.tar.gz |
Release files / CFFIpp-0.1.0.dev2.tar.gz
| Download URL | CFFIpp-0.1.0.dev2.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10ba373dee964c50358f6705bbc6eb219c03abbf23afe61d23d6c9ef060822dd
|
|
BLAKE2b-256 checksum How to use checksums |
0ce8955f88d220d75f4a861fe4a44d4af2d40e44487400ed5ddc81ae886f7ca3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for CFFIpp 0.1.0.dev2
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.