You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/source/whatsnew.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ Guided Upgrade
52
52
**************
53
53
This guide should help to make the upgrade as painless as possible, hence it points out where to start, and what to look out for.
54
54
55
-
* Have a look atthe CHANGES log file and read all important changes about0.3 for an overview.
55
+
* Have a look athttps://github.com/gitpython-developers/GitPython/blob/0.3/doc/source/changes.rst
56
56
* Start applying the renames, generally the ``utils`` modules are now called ``util``, ``errors`` is called ``exc``.
57
57
* Search for occurrences of the ``sha`` property of object instances. A similar value can be obtained through the new ``hexsha`` property. The native sha1 value is the ``binsha`` though.
58
58
* Search for code which instantiates objects directly. Their initializer now requires a 20 byte binary Sha1, rev-specs cannot be used anymore. For a similar effect, either convert your hexadecimal shas to binary shas beforehand ( ``binascii.unhexlify`` for instance ), or use higher level functions such as ``Object.new``, ``Repo.commit`` or ``Repo.tree``. The latter ones takes rev-specs and hexadecimal sha1 hashes.