Commitba878ef

committed

Reword partial_to_complete_sha_hex note

The git.db.partial_to_complete_sha_hex docstring refers to"AmbiguousObjects", suggesting the existence of an AmbiguousObjecttype (or an AmbiguousObjects type).Since there appears to be no such type in GitPython (or in gitdb),this seems to have been written in reference to the conditionexpressed by the AmbiguousObjectName exception, which the notesays is not currently able to be raised (such that BadObject israised instead) in situations where it would apply.Since the connection to that exeception is already clear fromcontext, this commit changes the wording to "ambiguous objects" toavoid being misread as a reference to a Python class of ambiguousobjects.

1 parent8bb882e commitba878efCopy full SHA for ba878ef

File tree

1 file changed

-1

lines changed

git
- db.py

1 file changed

-1

lines changed

`‎git/db.py`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -59,7 +59,7 @@ def partial_to_complete_sha_hex(self, partial_hexsha: str) -> bytes:`
`59`	`59`	`:raise BadObject:`
`60`	`60`
`61`	`61`	:note: Currently we only raise :class:`BadObject` as git does not communicate
`62`		`-AmbiguousObjects separately.`
	`62`	`+ambiguous objects separately.`
`63`	`63`	`"""`
`64`	`64`	`try:`
`65`	`65`	`hexsha,_typename,_size=self._git.get_object_header(partial_hexsha)`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Commitba878ef

File tree

1 file changed

1 file changed

`‎git/db.py`

0 commit comments