Using standard setuptools for package instalalation

DRL / blobtools

Modular command-line solution for visualisation, quality control and taxonomic partitioning of genome datasets

GNU General Public License v3.0

187 stars 44 forks source link

Using standard setuptools for package instalalation #15

Closed mmokrejs closed 8 years ago

mmokrejs commented 8 years ago

Hi, would you mind using setuptools to install your files site-wide? It seemed all *.py should be placed to /usr/bin but that does not work because ./lib/ is missing.

$ /usr/bin/covplot.py
Traceback (most recent call last):
  File "/usr/bin/covplot.py", line 47, in <module>
    import lib.BtCore as bt
ImportError: No module named lib.BtCore
$

Thank you

DRL commented 8 years ago

Hi mmokrejs,

I will look into it.

Was it not possible for you to install blobtools using virtualenv?

cheers,

dom

mmokrejs commented 8 years ago

Hi, I am sorry, I haven't even tried. I always try to install apps into a system-wide location as a package ... I use Gentoo Linux and typically create a package definition file so that the application is installed through standard package manager. And, although one could define the procedure manually, it is easier if the package uses setuptools -- it is then very simple. I am sure other will appreciate this as well.

mmokrejs commented 7 years ago

I think it would be helpful to restructure the code so that the importable modules were installed in some standard path where python can find them. Looking for them in ./lib/ is too bad.