pyBigWig
Hi,
We needed to use pyBigWig for some of our processing.
https://pypi.python.org/pypi/pyBigWig/0.3.2 or
https://github.com/dpryan79/pyBigWig
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.
http://woldlab.caltech.edu/woldlab-apt/pool/main/p/pybigwig/pybigwig_0.
3.2-0.dsc
But the pyBigWig package includes the source of the authors libBigWig
library: https://github.com/dpryan79/pyBigWig/tree/master/libBigWig
And instead of building a shared library, they just add the C files to
the python C extension. See:
https://github.com/dpryan79/pyBigWig/blob/master/setup.py#L14
I believe this is a violation of Debian packaging policy, but this
seems useful, what should one do in this case?
Diane
Reply to: