GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing pypi.org — GitPython GitPython 3.2.1GitPython is a Python library used to interact with Git repositories pip install GitPython
Gitoxide: A peek into the future…I started working on GitPython in 2009, back in the days when Python was 'my thing' and I had great plans with it. Of course, back in the days, I didn't really know what I was doing and this shows in many places. Somewhat similar to Python this happens to be 'good enough', but at the same time is deeply flawed and broken beyond repair. By 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. The community is maintaining the software and is keeping it relevant for which I am absolutely grateful. For the time to come I am happy to continue maintaining GitPython, remaining hopeful that one day it won't be needed anymore. 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
probably the skills to scratch that itch of mine: implement If you like the idea and want to learn more, please head over to gitoxide, an implementation of 'git' in Rust. (Please note that GitPythonGitPython is a python library used to interact with git repositories, high-level like git-porcelain, or low-level like git-plumbing. It provides abstractions of git objects for easy access of repository data often backed by calling the DEVELOPMENT STATUSThis project is in maintenance mode, which means that
The project is open to contributions of all kinds, as well as new maintainers. REQUIREMENTSGitPython needs the
The list of dependencies are listed in INSTALLGitPython 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. From PyPITo obtain and install a copy from PyPI, run: pip install GitPython
(A distribution package can also be downloaded for manual installation at the PyPI page.) From downloaded source codeIf you have downloaded the source code, run this from inside the unpacked pip install .
By cloning the source code repositoryTo clone the the GitHub repository from source to work on the code, you can do it like so: git clone https://github.com/gitpython-developers/GitPython
cd GitPython
./init-tests-after-clone.sh
On Windows, If you are cloning your own fork, then replace the above gh repo clone GitPython
Having cloned the repo, create and activate your virtual environment. Then make an editable install: pip install -e ".[test]"
In the less common case that you do not want to install test dependencies, With editable dependencies (not preferred, and rarely needed)GitPython, gitdb, and smmap live in this repository as independently packaged projects. To work on all three at once, install each one editably in the same virtual environment: pip install -e smmap -e gitdb -e ".[test]"
You can use To reiterate, this approach should only rarely be used. For most development it is preferable to allow the gitdb and smmap dependencices to be retrieved automatically from PyPI in their latest stable packaged versions. LimitationsLeakage of System ResourcesGitPython is not suited for long-running processes (like daemons) as it tends to
leak system resources. It was written in a time where destructors (as implemented
in the In case you still want to use it in such a context, you will want to search the
codebase for Another way assure proper cleanup of resources is to factor out GitPython into a separate process which can be dropped periodically. Windows supportSee Issue #525. RUNNING TESTSImportant: Right after cloning this repository, please be sure to have executed
the Install test dependenciesEnsure testing libraries are installed. This is taken care of already if you installed with: pip install -e ".[test]"
If you had installed with a command like Test commandsTo test, run: pytest
To lint, and apply some linting fixes as well as automatic code formatting, run: pre-commit run --all-files
This includes the linting and autoformatting done by Ruff, as well as some other checks. To typecheck, run: mypy
CI (and tox)Style and formatting checks, and running tests on all the different supported Python versions, will be performed:
Configuration filesSpecific tools are all configured in the
Orchestration tools:
ContributionsPlease have a look at the contributions file. INFRASTRUCTURE
How to make a new release
Projects using GitPython
LICENSE3-Clause BSD License, also known as the New BSD License. See the LICENSE file. One file exclusively used for fuzz testing is subject to a separate license, detailed here. This file is not included in the wheel or sdist packages published by the maintainers of GitPython. Project linksKey datesPyPI dataData sourced directly from PyPI's database.
2 maintainersPyPI dataData sourced directly from PyPI's database.
CreditsAuthor: Sebastian Thiel LicenseBSD-3-Clause RequiresPython >=3.8 Provides Extra
Tags
Classifiers
MetadataProject linksKey datesPyPI dataData sourced directly from PyPI's database.
2 maintainersPyPI dataData sourced directly from PyPI's database.
CreditsAuthor: Sebastian Thiel LicenseBSD-3-Clause RequiresPython >=3.8 Provides Extra
Tags
Classifiers
Release files for GitPython 3.2.1For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation. Source distribution (sdist)
Built distribution (wheel)
Total release size: 473.2 kB Release files / gitpython-3.2.1.tar.gz
Release files / gitpython-3.2.1-py3-none-any.whl
Security for GitPython 3.2.1ProvenanceProvenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats. No provenance foundNone of the files in this release were uploaded with provenance metadata. A note on package securityPyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package. To learn more about protecting yourself from malicious actors, visit our package security documentation. Release history Release notifications | RSS feed
Yanked reason: Aggressive unconditional timeout will fail long-running git operations
Yanked reason: 3.1.19wrong version for typing break installation
Yanked reason: Breaks older versions of python 3.5, 3.5.2 notably, due to typing | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |
