Tutorial
First create a Gihub instance:
from github import Github g = Github( "user", "password" )
Then play with your Github objects:
for repo in g.get_user().get_repos():
print repo.name
repo.edit( has_wiki = False )
You can also create a Github instance with an OAuth token:
g = Github( token )
Or without authentication:
g = Github()
Reference documentation
4 maintainers
Metadata
4 maintainers
Release files for PyGithub 1.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 | |
|---|---|---|---|---|
| PyGithub-1.3.zip | 102.3 kB | Without provenance | Details |
Release files / PyGithub-1.3.zip
| Download URL | PyGithub-1.3.zip |
|---|---|
| Size | 102.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4953433fdec4ae81692d88323f353067a74d38419ea8cd4836392b8231d015c
|
|
BLAKE2b-256 checksum How to use checksums |
600a72dfd61943e56379fab0c1af789641e108d4ed72b6f4137475b6f8c4cba2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for PyGithub 1.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.
