# PARAVIEW\_USE\_UNIFIED\_BINDINGS = ON will not build
**URL:** https://discourse.paraview.org/t/paraview-use-unified-bindings-on-will-not-build/941
**Category:** Development
**Tags:** python
**Created:** [November 20, 2018, 9:18pm UTC](https://discourse.paraview.org/t/paraview-use-unified-bindings-on-will-not-build/941 "2018-11-20T21:18:54Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@raymon68](https://discourse.paraview.org/u/raymon68)
#### Post date: [November 20, 2018, 9:18pm UTC](https://discourse.paraview.org/t/paraview-use-unified-bindings-on-will-not-build/941/1 "2018-11-20T21:18:54Z")
I am trying to get a Python Binding of the SpyPlotReader family of components. I am working an App were I need to import spcth files. VTK does not have this family of readers.
I have tried this build using Paraview versions 5.4 through nightly and it does not work.
Any ways when I try to compile with the intent of having a python binding for every CS wrapping I get the following error:
```
[61%] Building CXX object Wrapping/ClientServer/CMakeFiles/vtkPVVTKExtensionsDefaultCS.dir/vtkPVVTKExtensionsDefaultCSInit.cxx.o
/home/rmoral/build/build2/Wrapping/ClientServer/vtkPVVTKExtensionsDefaultCSInit.cxx: In function ‘void vtkPVVTKExtensionsDefaultCS_Initialize(vtkClientServerInterpreter*)’:
/home/rmoral/build/build2/Wrapping/ClientServer/vtkPVVTKExtensionsDefaultCSInit.cxx:51:63: error: invalid conversion from ‘void (*)()’ to ‘PyObject* (*)()’ {aka ‘_object* (*)()’} [-fpermissive]
PyImport_AppendInittab("vtkPVVTKExtensionsDefaultPython", initvtkPVVTKExtensionsDefaultPython);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/python3.6m/Python.h:124,
from /home/rmoral/build/ParaView-5.6.0-311-g25d4aa022a/VTK/Utilities/Python/vtkPython.h:80,
from /home/rmoral/build/build2/Wrapping/ClientServer/vtkPVVTKExtensionsDefaultCSInit.cxx:7:
/usr/include/python3.6m/import.h:121:17: note: initializing argument 2 of ‘int PyImport_AppendInittab(const char*, PyObject* (*)())’
PyObject* (*initfunc)(void)
~~~~~~~~~~~~^~~~~~~~~~~~~~~
make[2]: *** [Wrapping/ClientServer/CMakeFiles/vtkPVVTKExtensionsDefaultCS.dir/build.make:63: Wrapping/ClientServer/CMakeFiles/vtkPVVTKExtensionsDefaultCS.dir/vtkPVVTKExtensionsDefaultCSInit.cxx.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:51384: Wrapping/ClientServer/CMakeFiles/vtkPVVTKExtensionsDefaultCS.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
```
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [November 21, 2018, 7:03pm UTC](https://discourse.paraview.org/t/paraview-use-unified-bindings-on-will-not-build/941/2 "2018-11-21T19:03:16Z")
Unified bindings was an experiment which didn’t meet its goals, so it has sort of bit-rotted.
> Any ways when I try to compile with the intent of having a python binding for every CS wrapping I get the following error:
With unified bindings, CS wrapping _assumes_ Python wrapping exists. It doesn’t force its creation. The proper way is to do Python wrapping of the required modules similarly to how CS bindings are created.
---
### Author:  [@raymon68](https://discourse.paraview.org/u/raymon68)
#### Post date: [November 21, 2018, 7:09pm UTC](https://discourse.paraview.org/t/paraview-use-unified-bindings-on-will-not-build/941/3 "2018-11-21T19:09:17Z")
Okay.
So how does one build paraview so the build creates Python wrapping of the SpyPlot file readers?
I have not been able to find that option.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [November 27, 2018, 6:54pm UTC](https://discourse.paraview.org/t/paraview-use-unified-bindings-on-will-not-build/941/4 "2018-11-27T18:54:59Z")
`PARAVIEW_ENABLE_PYTHON` should do it.