Doesn't work where python 2 is default about guet HOT 6 CLOSED

My guess is that something is wrong with the shebang in the hooks. They look like #! /usr/bin/env python, and I think switching them to #! /usr/bin/env python3 will do the trick. However, even if that solves the problem on Linux, I'm not sure how it'll behave on other systems.

from guet.

I ran into this on Mac OSX as well where Python2 was the default installation. Python 3 is installed via homebrew at /usr/local/bin/python3.

At first, when trying to commit, I saw the module error and the commit didn't go through. After making the change you recommended above, I still see the module error, but the commit does go through.

Any thoughts?

from guet.

It's probably the post-commit hook throwing that error. The post-commit hook rotates who is considered the "author" of the commit, but nothing else. It won't stop you from development, you'll just lose out of that piece.

I'm working on a fix that'll let you initialize the commit hooks to explicitly use python3 rather than whatever the system default python is with a --python3 flag.

from guet.

This should be addressed in ec09fd2. If you pull down the most recent version from pypi and delete the current git hooks, you should be able to remake them with the --python3 flag.

from guet.

Your most recent change works, thanks! Maybe there should be a READMe note as well documenting this option?

from guet.

Done!

from guet.