GitHubParser
GitHubParser is a Python package designed to interact with the GitHub API, providing a suite of tools to fetch and parse data from GitHub repositories. It simplifies the process of accessing repository statistics, contents, and metadata, making it easier for developers to integrate GitHub data into their applications.
Features
-
Fetch Repository Statistics: Retrieve detailed statistics for any GitHub repository.
-
Access Repository Contents: Get the contents of specific paths within a repository.
-
List All Repositories: Fetch all repositories for a given GitHub user.
-
Rate Limit Information: Check the current rate limit status of the GitHub API.
-
Configuration File Parsing: Parse configuration files to retrieve GitHub API credentials and other settings.
-
Customizable Parsing: Supports custom parsing of URLs and APIs.
Installation
You can install GitHubParser using pip:
pip install gh-parser
Usage
To use GitHubParser, you need to create an instance of the GitHubParser class and provide your GitHub API credentials. You can then use the various methods provided by the class to fetch and parse data from GitHub repositories.
Here's an example of how you can use GitHubParser to fetch statistics for a GitHub repository:
from gh_parser import GitHubParser
# Create an instance of GitHubParser
parser = GitHubParser(username='your_username', token='your_token')
# Alternatively, you can provide your credentials in a configuration file
parser = GitHubParser(config_file='config.ini')
# Fetch API Information
main_page = parser.get_main_page()
repostats = parser.full_stats
all_repos = parser.all_repos
all_repopaths = parser.all_repopaths
# Alternatively, you can use the custom functions to fetch specific data
from gh_parser import get_repo_stats, get_repo_contents,
get_all_repos, get_rate_limit
# Fetch repository statistics
repo_stats = get_repo_stats(config_file='config.ini')
Metadata
Release files for gh-parser 1.0.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 | |
|---|---|---|---|---|
| gh_parser-1.0.3.tar.gz | 17.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gh_parser-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.1 kB
Release files / gh_parser-1.0.3.tar.gz
| Download URL | gh_parser-1.0.3.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1200137c3c383b9ea8e988a4cb2cd01f8d7b7a8bcec25ce84c977b347a689727
|
|
BLAKE2b-256 checksum How to use checksums |
47cf85a01ebb85b80b662c9e010ffb62f7ae5285cd67506535c0d765e83e577a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.0
|
Release files / gh_parser-1.0.3-py3-none-any.whl
| Download URL | gh_parser-1.0.3-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
623cc2aa8f7fa249f4d548a875b5b498641dbcbb01045b95112ef16de5691efc
|
|
BLAKE2b-256 checksum How to use checksums |
1c813f66528babd3455563067041b3d32d38f5cf06c15680ea9f83b56eae9d14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.0
|
Security for gh-parser 1.0.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.