Closed danmackinlay closed 14 years ago
Yep, while I may not be able to attach diffs, I will hold off doing so until there is a policy call fro you on this one. Forcing GitPython==0.1.6 causes github-tools to work perfectly (not even any nasty SystemExits). So I suspect requires.txt needs to ahve the line
GitPython>=0.1.6
changed to be
GitPython==0.1.6
Or is tracking the new GitPython desirable?
I changed GitPython requirement. Requires version 1.6 specifically.
github-tools 0.3 will track GitPython 2.x.
I will fix issue 17 and release 0.2 with the fix. Then I will apply your changes.
Thanks.
Thanks for that terrifyingly fast fix!
(formerly: "paver gh_pages_create throws an AttributeError: 'function' object has no attribute 'endswith')
On a fresh checkout of github-tools I get weird behaviour on working though the instructions in the readme file. When I get to the step paver gh_pages_create, i get a nasty traceback:
Dropping into the debugger... the problem in gh_pages.py seems to occur on line 304:
AFAICT that will return a lambda which when called executes the fucntion
git-dir
against the site repo, which doesn't seem right. It seems like that line should be something likeThen we need to update line 228 from
to
for the same reason, i.e. api differences between the expected and supplied gitpython Repo object. Assuming i can attach things to github issues I'll attach a diff to that effect.
on my system, if i make those changes i then get a nasty uninformative error:
which may be about my git throwing nasty errors or something? My time to debug this is momentarily at an end, however, so let's see if I'm just doing something stupid first.
Anyway, there's something awry here with gitpython api. import git; git.version reports "0.2.0-beta1" - is the solution here as simple as pegging the version of gitpython in the requirements to 0.1?