I cloned the project, and hit python setup.py develop, when BAM, this.
Obviously, you're importing in setup.py the version which causes everything to get imported before actually installing the project, and therefore one would have to install all dependencies by hand prior to calling setup.py develop.
Traceback (most recent call last):
File "setup.py", line 2, in <module>
from ytfs import __version__
File "/home/3pillar.corp/vlad.ardelean/tmp/clones/ytfs/ytfs/__init__.py", line 1, in <module>
from .ytfs import __version__
File "/home/3pillar.corp/vlad.ardelean/tmp/clones/ytfs/ytfs/ytfs.py", line 20, in <module>
from fuse import FUSE, FuseOSError, Operations
ImportError: No module named 'fuse'
To lazy to submit a PR, but when you (or someone) get(s) to it, it should be a quick fix.
I cloned the project, and hit
python setup.py develop
, when BAM, this.Obviously, you're importing in setup.py the version which causes everything to get imported before actually installing the project, and therefore one would have to install all dependencies by hand prior to calling
setup.py develop
.I found a nice answer on stack overflow on how to better specify the
__version__
attribute http://stackoverflow.com/questions/17583443/what-is-the-correct-way-to-share-package-version-with-setup-py-and-the-packageTo lazy to submit a PR, but when you (or someone) get(s) to it, it should be a quick fix.