build/

PAPEROPT_a4 = -D latex_paper_size=a4

PAPEROPT_letter = -D latex_paper_size=letter

ALLSPHINXOPTS = -d_build/doctrees$(PAPEROPT_$(PAPER))$(SPHINXOPTS).

ALLSPHINXOPTS = -dbuild/doctrees$(PAPEROPT_$(PAPER))$(SPHINXOPTS)source

.PHONY: help clean html web pickle htmlhelp latex changes linkcheck

@echo" linkcheck to check all external links for integrity"

clean:

-rm -rf_build/*

-rm -rfbuild/*

html:

mkdir -p_build/html_build/doctrees

$(SPHINXBUILD) -b html$(ALLSPHINXOPTS)_build/html

mkdir -pbuild/htmlbuild/doctrees

$(SPHINXBUILD) -b html$(ALLSPHINXOPTS)build/html

@echo

@echo"Build finished. The HTML pages are in_build/html."

@echo"Build finished. The HTML pages are inbuild/html."

pickle:

mkdir -p_build/pickle_build/doctrees

$(SPHINXBUILD) -b pickle$(ALLSPHINXOPTS)_build/pickle

mkdir -pbuild/picklebuild/doctrees

$(SPHINXBUILD) -b pickle$(ALLSPHINXOPTS)build/pickle

@echo

@echo"Build finished; now you can process the pickle files."

web: pickle

json:

mkdir -p_build/json_build/doctrees

$(SPHINXBUILD) -b json$(ALLSPHINXOPTS)_build/json

mkdir -pbuild/jsonbuild/doctrees

$(SPHINXBUILD) -b json$(ALLSPHINXOPTS)build/json

@echo

@echo"Build finished; now you can process the JSON files."

htmlhelp:

mkdir -p_build/htmlhelp_build/doctrees

$(SPHINXBUILD) -b htmlhelp$(ALLSPHINXOPTS)_build/htmlhelp

mkdir -pbuild/htmlhelpbuild/doctrees

$(SPHINXBUILD) -b htmlhelp$(ALLSPHINXOPTS)build/htmlhelp

@echo

@echo"Build finished; now you can run HTML Help Workshop with the"\

latex:

mkdir -p_build/latex_build/doctrees

$(SPHINXBUILD) -b latex$(ALLSPHINXOPTS)_build/latex

mkdir -pbuild/latexbuild/doctrees

$(SPHINXBUILD) -b latex$(ALLSPHINXOPTS)build/latex

@echo

@echo"Build finished; the LaTeX files are in_build/latex."

@echo"Build finished; the LaTeX files are inbuild/latex."

@echo"Run\`make all-pdf' or\`make all-ps' in that directory to"\

changes:

mkdir -p_build/changes_build/doctrees

$(SPHINXBUILD) -b changes$(ALLSPHINXOPTS)_build/changes

mkdir -pbuild/changesbuild/doctrees

$(SPHINXBUILD) -b changes$(ALLSPHINXOPTS)build/changes

@echo

@echo"The overview file is in_build/changes."

@echo"The overview file is inbuild/changes."

linkcheck:

mkdir -p_build/linkcheck_build/doctrees

$(SPHINXBUILD) -b linkcheck$(ALLSPHINXOPTS)_build/linkcheck

mkdir -pbuild/linkcheckbuild/doctrees

$(SPHINXBUILD) -b linkcheck$(ALLSPHINXOPTS)build/linkcheck

@echo

@echo"Link check complete; look for any errors in the above output"\

sys.path.insert(0,os.path.abspath('../lib'))

sys.path.insert(0,os.path.abspath('../../lib'))

extensions= ['sphinx.ext.autodoc','sphinx.ext.doctest']

templates_path= ['templates']

templates_path= ['.templates']

exclude_trees= ['_build']

exclude_trees= ['build']

html_static_path= ['static']

html_static_path= ['.static']

GitPython 0.3 is the first step in creating a hybrid which uses a pure python implementations for all simple git features which can be implemented without significant performance penalties. Everything else is still performed using the git command, which is nicely integrated and easy to use.

Its biggest strength, being the support for all git features through the git command itself, is a weakness as well considering the possibly vast amount of times the git command is being started up. Depending on the actual command beingperformaned, the git repository will be initialized on many of these invocations, causing additional overhead for possibly tiny operations.

Its biggest strength, being the support for all git features through the git command itself, is a weakness as well considering the possibly vast amount of times the git command is being started up. Depending on the actual command beingperformed, the git repository will be initialized on many of these invocations, causing additional overhead for possibly tiny operations.

Keeping as many major operations in the python world will result in improved caching benefits as certain data structures just have to be initialized once and can be reused multiple times. This mode of operation may improve performance when altering the git database on a low level, and is clearly beneficial on operating systems where command invocations are very slow.

Why you should not upgrade

GitPython 0.3 in most cases will not run faster than GitPython 0.2, the opposite might be the case at it uses the pure python implementation by default.

There have been a few renames which will need additional adjustmentsby your code.

There have been a few renames which will need additional adjustmentsin your code.

Generally, if you only read git repositories, version 0.2 is sufficient and very well performing.