init_RANS functions

[cekees]

@JohanMabille I was doing some local testing of the RANS3PSed class (just merged your PR #1133) and noticed some 2D calls in the 3D pybind11 wrappers:

$ grep init_RANS *.cpp
RANS3PF2D.cpp:void init_RANS3PF2D(py::module& m)
RANS3PF.cpp:void init_RANS3PF2D(py::module& m);
RANS3PF.cpp:    init_RANS3PF2D(m);
RANS3PSed2D.cpp:void init_RANS3PFSed2D(py::module& m)
RANS3PSed.cpp:void init_RANS3PFSed2D(py::module& m);
RANS3PSed.cpp:    init_RANS3PFSed2D(m);

I think it probably works fine anyway (just a naming issue), but can you explain what is going on here? I noticed that the RANS2P wrappers don't declare or call a module init function.

[JohanMabille]

RANS2P and RANS2P2D are actually two separate Python extensions. RANS3PF and RANS3PF2D sill belong to the same Python extension, I just split the bindings in two separate cpp files. This reduces the amount of memory required for building each of these cpp files while not requiring any change on the Python side.

The cpp file defining the bindings still has to bind both classes, thus the init_XXX function.