Repository navigation
Installing gitdb and gitdb2 simultaneously breaks gitdb package #908
Description
Activity
(This broke our CI/CD system is some difficult to figure out ways)
Workaround: pin this package with:
GitPython<3in your requirements.txtThanks so much for pointing this out! I have just removed that line, hoping that this will fix the issue. Maybe you can provide the complete line that would pin
gitdbtoGitPython < 3, maybe that's better.The provided line will pin the GitPython package to a version less than 3.0.0:
GitPython<3That's a valid
requirements.txtentry.Thank you. Excuse my ignorance, I don't understand how a line like this would fit into the
requirements.txtfile of GitPython itself. Isn't that self-referential? I thought there is a way to constrain requirements to certain conditions, like:use gitdb only if GitPython's version is smaller than 3.In any case, looking at the fix I made in ca080bb, do you think this will work for you?
Yes, that totally fixed it.
@Harmon758 If I remember correctly, these two requirements broke someones build in strange ways. I am not knowledgable enough though if it ultimately was a problem with GitPython.
If you see issues with the current state ofrequirements.txt, I welcome a PR to fix it. Right now it seems quite minimal.
The change to
requirements.txtin 2e7e82b specifies that bothgitdb2andgitdbbe installed. As installation packages they share the same name and step on each other.This breaks the use of the module like this: