it's phased out only in the master branch of git-python, which never saw the light of the day.
Gitdb is not actively developed anymore, at least not by me.
Please close this issue if you find this explanation sufficient.
My report links to the line in setup.py in the master branch which requires gitdb. So if I understand you correctly, that requirement can be deleted. Is that correct?
I see the only traces of gitdb in master are in test_* files and fixtures, and in documentation.
If I understand it right, tests use the gitdb repo to test against, which makes it a test dependency. That would mean this repo has changed into a test fixture.
Running GitPython tests fail missing async, smmap, mock and dulwich modules. I'll update its setup.py when I get a chance.
Activity
Byron commented on Aug 15, 2014
it's phased out only in the master branch of git-python, which never saw the light of the day.
Gitdb is not actively developed anymore, at least not by me.
Please close this issue if you find this explanation sufficient.
jean commented on Aug 15, 2014
My report links to the line in setup.py in the master branch which requires gitdb. So if I understand you correctly, that requirement can be deleted. Is that correct?
Byron commented on Aug 17, 2014
In master, that should be possible, yes. Even though it might not make a difference as I wouldn't consider master ready for production.
jean commented on Aug 18, 2014
I see the only traces of gitdb in master are in test_* files and fixtures, and in documentation.
If I understand it right, tests use the gitdb repo to test against, which makes it a test dependency. That would mean this repo has changed into a test fixture.
Running GitPython tests fail missing async, smmap, mock and dulwich modules. I'll update its setup.py when I get a chance.
jean commented on Sep 15, 2014
Added in gitpython-developers/GitPython#190