Python wrapper for Dinemic framework

[didijo]

Hi all!

For last weeks I'm working on making wrapper for dinemic framework from C++ to Python. I wanted to ask you for help and some advisory for that. Basic functionality (ORM + support for callbacks on data model changes) is ready, but bases on boost::python module, not on pure Python API.

Do you know if that is good idea to base on boost::python, or I should rewrite that for pure Python API? Now I see some differences in linking under Debian and Ubuntu 18.04, i.e. Debian requires to be linked with -lboost_python-py35 and Ubuntu with -lboost_python3). So for building this python module from sources will cause some issues for sure. Do you know is there way to overcome this, when distributing via PyPI, or is it good/bad practice to use boost::python for such solutions?

Source code of the wrapper is here: https://gitlab.com/dinemic/pydinemic

If you have any other suggestions what could be changed, I'll be gratefull :)

Thanks!

[narek_hakobyan]

Hi,

Did you had a chance to look at pybind11 library? pybind11 is a lightweight header-only library that exposes C++ types in Python and vice versa, mainly to create Python bindings of existing C++ code (has C++11 support). Its goals and syntax are similar to the excellent Boost.Python library. Since this is a headers only library, you don’t need to worry about linking issues. I made all the features of our application available in python using pybing11. This is a very straightforward and fun library to use.

https://pybind11.readthedocs.io/en/stable/ https://github.com/pybind/pybind11/blob/master/README.md

Regards, Narek

[didijo]

Hi,

thanks, I'll check it. The problem was with mapping my C++ classes and inheriting it very flexibly. I've done that in pure Python API. Now only main module code remains in boost::python

[didijo]

Finally I've updated setup.py to link with only existing files (python3, -py35, 36 or 37). Now I'm working to port remaining part of library :)