AttributeError: 'GitUp' object has no attribute 'git'
martin-ueding opened this issue · comments
I updated to v1.1.0 via
pip install --user -U git-up
and just tried it out in my repo. I got the following:
Traceback (most recent call last):
File "/home/mu/.local/bin/git-up", line 9, in <module>
load_entry_point('git-up==1.1.0', 'console_scripts', 'git-up')()
File "/home/mu/.local/bin/gitup.py", line 552, in run
gitup = GitUp()
File "/home/mu/.local/bin/gitup.py", line 110, in __init__
self.load_config()
File "/home/mu/.local/bin/gitup.py", line 408, in load_config
value = self.config(key)
File "/home/mu/.local/bin/gitup.py", line 423, in config
return self.git.config('git-up.{0}'.format(key))
AttributeError: 'GitUp' object has no attribute 'git'
Am I missing a dependency or so?
Strange, I've tested it and it worked. Gonna investigate right now.
Please try re-installing git-up. If pip doesn't want to, please report here and I'll release the fix as a new version (now I've just updated v1.1.0)
pip does not update since it has the current version. A new version would probably be easier.
Okay, new version should be released in some minutes.
So, v1.1.1 is released. I hope, all problems are fixed, finally.
Okay, I did pip install --user -U git-up, it updated, but git-up --version gives me:
GitUp version is: v1.1.0
Recent version is: v1.1.1
Run 'pip install -U git-up' to get the update.
In the /home/mu/.local/bin/git-up, I see a reference to 1.1.0, is that correct?
No, there is still something messed up. I updated using the same command and got GitUp version is: v1.1.1. What is the output of pip install --user -U git-up? In addition, what does pip show git-up say?
Output of mu:~ pip install --user -U git-up:
Downloading/unpacking git-up from https://pypi.python.org/packages/source/g/git-up/git-up-1.1.1.zip#md5=22452bb518f519f6c01f1e46f6669d59
Running setup.py egg_info for package git-up
Requirement already up-to-date: GitPython==0.3.2.RC1 in ./.local/lib/python2.7/site-packages (from git-up)
Requirement already up-to-date: colorama==0.2.5 in ./.local/lib/python2.7/site-packages (from git-up)
Requirement already up-to-date: termcolor==1.1.0 in ./.local/lib/python2.7/site-packages (from git-up)
Requirement already up-to-date: docopt==0.6.1 in ./.local/lib/python2.7/site-packages (from git-up)
Requirement already up-to-date: gitdb>=0.5.1 in ./.local/lib/python2.7/site-packages (from GitPython==0.3.2.RC1->git-up)
Requirement already up-to-date: async>=0.6.1 in ./.local/lib/python2.7/site-packages (from gitdb>=0.5.1->GitPython==0.3.2.RC1->git-up)
Requirement already up-to-date: smmap>=0.8.0 in ./.local/lib/python2.7/site-packages (from gitdb>=0.5.1->GitPython==0.3.2.RC1->git-up)
Installing collected packages: git-up
Found existing installation: git-up 1.1.0
Uninstalling git-up:
Successfully uninstalled git-up
Running setup.py install for git-up
changing mode of /home/mu/.local/bin/gitup.py to 775
Installing git-up script to /home/mu/.local/bin
Successfully installed git-up
Cleaning up...
Output of pip show git-up:
---
Name: git-up
Version: 1.1.0
Location: /home/mu/.local/lib/python2.7/site-packages
Requires: GitPython, colorama, termcolor, docopt
Seems like you're using an old version of pip. Older versions of pip are known for funky behaviour when trying to upgrade packages (see #4 a similar problem). Could you try removing pip's build dir (/tmp/pip-build-*, ~/.pip, ~/tmp/pip-build-*) and then re-run the install-command?
I rebooted the computer, and tried it again. It works now, and git up
works for my project without any remotes. Thank you for your work!
No problem, you're welcome :)