Guidelines for packaging projects using pybind11

Hi,
I am greatly enjoying using pybind11. I am not sure if this question goes beyond the scope of this project, but I am sure I am not the only person dealing with this issue.

I have a mixed C++ / Python project, mainly a C++ library, a wrapper for this library using pybind11, some additional library functionality in pure python, using the pybind11 module, and lots of tests and usage samples in both C++ and Python.

So now, how can I properly package my library / SDK? The C++ part is easy, use CMake to build, and install/package. But how about my pure python files?
Do I call Python from CMake or rather CMake from Python, or is it possible to stay in CMake entirely?
The second link (it's the example linked in the documentation) unfortunately only builds the extension, but unfortunately does not distribute any other Python files with it.

How about my users? How would they like to install my module?
On Ubuntu, standard way would be to install a .deb package for my C++ SDK, and then use pip or setup.py for the python part. On Windows? SDK installer and then build the extensions for a specific Python version? Deliver prebuild extensions and register them with existing Python installations?

As I said, this might be (and probably is) beyond the scope of this project, but some additional pointers in the documentation would be very helpful.