This can be done in any order, and in separate pip install commands or the same one, so long as -e appears before each path. If you want to do that and you want the versions in GitPython's git submodules to be used, then pass -e git/ext/gitdb and/or -e git/ext/gitdb/gitdb/ext/smmap to pip install. This can be done by making editable installations of those dependencies in the same virtual environment where you install GitPython. In rare cases, you may want to work on GitPython and one or both of its gitdb and smmap dependencies at the same time, with changes in your local working copy of gitdb or smmap immediatley reflected in the behavior of your local working copy of GitPython. ![]() With editable dependencies (not preferred, and rarely needed) In the less common case that you do not want to install test dependencies, pip install -e. To obtain and install a copy from PyPI, run: GitPython and its required package dependencies can be installed in any of the following ways, all of which should typically be done in a virtual environment. The installer takes care of installing them for you. The GIT_PYTHON_GIT_EXECUTABLE= environment variable. If it is not in your PATH, you can help GitPython find it by setting GitPython needs the git executable to be installed on the system and available in your PATH for most operations. The project is open to contributions of all kinds, as well as new maintainers. …issues will be responded to with waiting times of up to a month.…there will be no bug fixes, unless they are relevant to the safety of users, or contributed.…there will be no feature development, unless these are contributed.This project is in maintenance mode, which means that It provides abstractions of git objects for easy access of repository data often backed by calling the git GitPython is a python library used to interact with git repositories, high-level like git-porcelain, If you like the idea and want to learn more, please head over to gitoxide, an Probably the skills to scratch that itch of mine: implement git in a way that makes tool creation a piece of cake for most. More than 15 years after my first meeting with 'git' I am still in excited about it, and am happy to finally have the tools and For the time to come I am happy to continue maintaining GitPython, remaining hopeful that one day it won't be needed anymore. ![]() The community is maintaining the software and is keeping it relevant for which I am absolutely grateful. Python this happens to be 'good enough', but at the same time is deeply flawed and broken beyond repair.īy now, GitPython is widely used and I am sure there is a good reason for that, it's something to be proud of and happy about. ![]() Of course, back in the days, I didn't really know what I was doing and this shows in many places. I started working on GitPython in 2009, back in the days when Python was 'my thing' and I had great plans with it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |