WIP: python binding/integration

[timkpaine]

• transfer pypi
• copyrights
• sub module?

[timkpaine]

ping @texodus and @deepankarsharma for thoughts on how to best do integrations.

[deepankarsharma]

At first glance the Python binding code looks super clean, nice job! I will do a more detailed review sometime tomorrow.

Some thoughts on how an integration could look like
a. We build all perspective cpp files into a shared library, lets say we call this libpsp
b. We add C++ tests using GTest which links against libpsp and tests the base C++ functionality (lets say we call this target psp_test).
c. We build a Python extension which links against libpsp (lets say pypsp)
d. In the future any other language extensions (Lua anyone?) can link against libpsp.
e. We add some integration tests and benchmark for python that use pypsp and test things end to end.
f. One other thing that might be worth thinking sooner rather than later is to have the notion of "versions" of the C++ code that is loaded for the Python / Javascript extension.

My preference would be for the Python (and future language bindings) to be licensed identically to Perspective under the same license and for the code to be merged into mainline (Rather than via submodules). Would love to hear thoughts from others about this.

[texodus]

Thanks for the PR!

This looks great but needs some work and planning before we can consider merge (or where even to merge it). I've cleaned it up a bit on the python branch for discussion & review.

I concur with @deepankarsharma on all points above, especially the question of licensing which is a critical consideration.