py-gitea
A simple API client for Gitea > 1.24 based on the idea that passing around dictionaries and strings is disgusting and needs to be wrapped in something safe. So, the whole implementation is focused on making access and working with Organizations, Teams, Repositories and Users as pain free as possible.
Most functions should be covered by tests or should be in use (somewhere) so things should work as expected. Note that not the full Swagger-API is accessible.
Originally forked from https://github.com/m301/py-gitea.
Usage
First get a gitea object wrapping access and authentication (via an api token) for your gitea instance:
from gitea import *
gitea = Gitea(URL, TOKEN)
Operations like requesting the Gitea version or authentication user can be done directly from the gitea object:
print("Gitea Version: " + gitea.get_version())
print("API-Token belongs to user: " + gitea.get_user().username)
Adding entities like Users, Organizations, ... also is done via the gitea object.
user = gitea.create_user("Test Testson", "test@test.test", "password")
All operations on entities in gitea are then accomplished via the according wrapper objects for those entities.
Each of those objects has a .request method that creates an
entity according to your gitea instance
other_user = User.request(gitea, "OtherUserName")
print(other_user.username)
or can be requested from other entities.
orgs = user.get_orgs()
print(f"{user.name} is in orgarnisations {orgs}")
Note that the fields of the User, Organization,... classes are dynamically created at runtime, and thus not visible during divelopment. Refer to the Gitea-API documentation for the fields names.
Fields that can not be altered via gitea-api, are read only. After altering a field, the .commit method of the
according object must be called to synchronize the changed fields with your gitea instance.
org = Organization.request(gitea, test_org)
org.description = "some new description"
org.location = "some new location"
org.commit()
An entity in gitea can be deleted by calling delete.
org.delete()
All entity objects do have methods to execute some of the requests possible though the gitea-api:
org = Organization.request(gitea, ORGNAME)
teams = org.get_teams()
for team in teams:
repos = team.get_repos()
for repo in repos:
print(repo.name)
If something is missing, feel free to add it :).
Installation
Use pip install py-gitea to install.
Tests
Tests can be run with:
python3 -m pytest test_api.py
Make sure to have a gitea-instance running on http://localhost:3000, and an admin-user token at .token.
The admin user must be named test, with email secondarytest@test.org.
1 maintainer
Metadata
1 maintainer
Release files for py-gitea 0.3.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| py_gitea-0.3.3.tar.gz | 26.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| py_gitea-0.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.6 kB
Release files / py_gitea-0.3.3.tar.gz
| Download URL | py_gitea-0.3.3.tar.gz |
|---|---|
| Size | 26.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ced304bbcf3e897e5b26894b138b0235311aa10f7bf1bc9a5890f0801b54457f
|
|
BLAKE2b-256 checksum How to use checksums |
6272c2bbb3ee7538b476d7fc87faec21e6e843d20a1c9ac0b1fba3e3a9172b09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance 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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency logRelease files / py_gitea-0.3.3-py3-none-any.whl
| Download URL | py_gitea-0.3.3-py3-none-any.whl |
|---|---|
| Size | 20.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9a5dfac8718084184783dc1a902c6abf86eefceb4459524148c22cef6cb25d7
|
|
BLAKE2b-256 checksum How to use checksums |
17b491a7cf989a4a7237054ef86185ee84a01797bab07c3ac9bdc27f5128c572
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance 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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency logSecurity for py-gitea 0.3.3
Provenance
Provenance 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for py_gitea-0.3.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency logA note on package security
PyPI 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.
