Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Note in GitCmdObjectDB should be removed or updated #1849

Closed
EliahKagan opened this issue Feb 29, 2024 · 1 comment · Fixed by #1850
Closed

Note in GitCmdObjectDB should be removed or updated #1849

EliahKagan opened this issue Feb 29, 2024 · 1 comment · Fixed by #1850

Comments

@EliahKagan
Copy link
Contributor

EliahKagan commented Feb 29, 2024

Somewhat similar to #1845, the git.db.GitCmdObjectDB docstring contains this note:

GitPython/git/db.py

Lines 34 to 35 in 87b8035

:note: For now, we use the git command to do all the lookup, just until we
have packs and the other implementations.

I think that note can simply be removed now, since as far as I know, it does not correspond to a current goal and is not needed to understand the code or how to use it. But I am not confident of this, because I am not sure exactly what it is actually referring to. If more features were implemented, would this have been:

  • A change to GitCmdObjectDB itself?
  • Switching back from GitCmdObjectDB to GitDB?
  • A combination of the two, or something else related?

That only needs to be answered if it affects what should happen in that docstring (or elsewhere), which is why I've made this an issue rather than a discussion question.

I plan to remove it in a forthcoming PR with a number of other docstring revisions, but I'm opening this in case my understanding is mistaken.

@Byron
Copy link
Member

Byron commented Feb 29, 2024

Thank you for sharing your findings!

That note was definitely referring to having a built-in implementation of the Git Object Database, which never manifested, and what was there was obviously too slow.

Thus, I think it's absolutely fair to remove the note.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants