|
@@ -5,7 +5,7 @@ kernel/git coding style.
|
|
|
|
|
|
|
|
Where possible include updates to NEWS along with your improvements.
|
|
Where possible include updates to NEWS along with your improvements.
|
|
|
|
|
|
|
|
-New functionality and bug fixes should be accompanied with matching unit tests.
|
|
+New functionality and bug fixes should be accompanied by matching unit tests.
|
|
|
|
|
|
|
|
Coding style
|
|
Coding style
|
|
|
------------
|
|
------------
|
|
@@ -29,8 +29,8 @@ unittest2 (which you will need to have installed) on older versions of Python.
|
|
|
String Types
|
|
String Types
|
|
|
------------
|
|
------------
|
|
|
Like Linux, Git treats filenames as arbitrary bytestrings. There is no prescribed
|
|
Like Linux, Git treats filenames as arbitrary bytestrings. There is no prescribed
|
|
|
-encoding for these strings, and although it is fairly common to use UTF-8, anything
|
|
+encoding for these strings, and although it is fairly common to use UTF-8, any
|
|
|
-can and is used as encoding with Git.
|
|
+raw byte strings are supported.
|
|
|
|
|
|
|
|
For this reason, Dulwich internally treats git-based filenames as bytestrings. It is up
|
|
For this reason, Dulwich internally treats git-based filenames as bytestrings. It is up
|
|
|
to the Dulwich API user to encode and decode them if necessary.
|
|
to the Dulwich API user to encode and decode them if necessary.
|
|
@@ -38,4 +38,3 @@ to the Dulwich API user to encode and decode them if necessary.
|
|
|
* git-repository related filenames: bytes
|
|
* git-repository related filenames: bytes
|
|
|
* object sha1 digests (20 bytes long): bytes
|
|
* object sha1 digests (20 bytes long): bytes
|
|
|
* object sha1 hexdigests (40 bytes long): str (bytestrings on python2, strings on python3)
|
|
* object sha1 hexdigests (40 bytes long): str (bytestrings on python2, strings on python3)
|
|
|
-
|
|
|
Jelmer Vernooij