missing convenient python object cache generation/distribution (+ possible filesystem cluttering on uninstall) about enjarify HOT 2 OPEN

I haven't tried creating a package using setup.py before. I'll have to look into that some time. The problem of course is that I run it from a git repo in my home directory, so that's what the directions assume.

from enjarify.

@Storyyeller you are speaking about the enjarify.sh and its directory discovery, right? This shouldn't be a problem at all, this could still work as is.
The only main difference would be that there is a setup.py that could be used if someone wants to install it into the system or package your software. In such case the /usr/lib/python3.5/site-packages/ is the target location (but you can of cause still run it normally from your home or whatever directory).

You can also tell setuptools setup.py to distribute non .py files (like the enjarify.sh) so you would have a base dir /usr/lib/python3.5/site-packages/enjarify where the enjarify.sh is inside and also the enjarify directory with the python modules (so its .../enjarify/enjarify) therefor everything behaves as currently.

This way i could call something like

python setup.py install -O1 --root="${pkgdir}"

and it would create the cache files and distribute everything system-wide (so i just have to create the /usr/bin/enjarify symlink).

from enjarify.