We needed to use pyBigWig for some of our processing.
Being able to read bigBed or bigWig and to be able to directly write
bigwig files seemed useful to us. The package is MIT/Expat licensed
I made a prototype package for us.
But the pyBigWig package includes the source of the authors libBigWig
And instead of building a shared library, they just add the C files to
the python C extension. See:
I believe this is a violation of Debian packaging policy, but this
seems useful, what should one do in this case?