Python package

[franciszekjuras]

Hi,
I have some experience with C++ and Python, but never written C/C++ extensions for Python. Do you think it could be possible to create Python package without much changes to current codebase? Or perhaps the best solution is to build the library and use ctypes for interfacing?

[sfilip]

Hi! Not really sure what to answer. Haven't considered building a Python interface to the tool until now. You're welcome to try something out. When I have some time, I'll try to explore what possibilities there are, but I can't guarantee that it will be very soon.

[gsmecher]

Since the library is implemented and exposed in c++, I suggest you look into pybind11 (as opposed to boost::python or ctypes). A pybind11 wrapper would not require any changes to the existing codebase at all. You will need to add another .cpp file containing Python bindings, and figure out how to integrate it into the build, release, and testing machinery.

A Python binding would be wonderful - but scipy.signal.remez has pride of place in the Python world and will not easily be dislodged by an module outside the scipy/numpy ecosystem (no matter how much better it is.) Since scipy also uses c++ extensions via pybind11, you should also consider whether it makes sense to add the c++ source to scipy (license willing) and accept that it may drift from this version.

[gsmecher]

See pr18.