codeorigins
https://github.com/idlesign/codeorigins
Description
Code origins contest based on GitHub data
CodeOrigins live: http://idlesign.github.io/codeorigins/
Find interesting people and projects originating in various countries;
See what countries produce most starred projects;
Know your impact on community of your favourite language;
and more.
FAQ
But wait, this data is not realtime!
Yes, these are static web-pages (see docs/) compiled from dumped data (see codeorigins/dump/). And it sure can be outdated.
And what if I want to see updated data?
You can dump data you’re interested in and make a pull request.
Quick and dirty start:
Fork repository;
Git pull forked repository into local directory;
$ cd to the directory;
$ pip install -e . (sudo may be required) - this will made codeorigins CLI available;
Use $ codeorigins dump (see below) without --into - this puts dumps into codeorigins/dump/;
Commit and push added/changed dumps;
Create a pull request on your GitHub repository page.
My country or language is not listed, what am I to do?
Edit codeorigins/settings.py, add all what you need and make a pull request. You can also make and submit new/updated dumps (see above).
CLI
codeorigins comes with CLI to streamline common actions.
Data Dump
Using rate-limited GitHub search API:
$ codeorigins dump --into /home/idle/ghdump --country ru --language Python api
This will use api to fetch repositories data for users located in Russia whose primary language is Python and dump it into /home/idle/ghdump.
Register OAuth Application (https://github.com/settings/developers) and use its Client ID and Client Secret to loosen the rate limits (append --credentials <id>,<secret> to dump command).
HTML Export
Use make_html command to read data from dumps and compose HTML:
$ codeorigins make_html --dump_dir /home/idle/ghdump
This will create HTML file in current working directory.
Settings
See supported countries and languages using the following command:
$ codeorigins show_settings
Requirements
Python 3.6+
click
Jinja2
requests
Metadata
Release files for codeorigins 0.3.1
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 | Actions |
|---|---|---|---|---|
| codeorigins-0.3.1.tar.gz | 16.3 kB | Without provenance | Details for codeorigins-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| codeorigins-0.3.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for codeorigins-0.3.1-py2.py3-none-any.whl |
Total release size: 35.1 kB
Release files / codeorigins-0.3.1.tar.gz
| Download URL | codeorigins-0.3.1.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a2bcbf298afa7df08692bbc06c7de6264b6ef1e9bf0388adbabb665405fbbbf
|
|
BLAKE2b-256 checksum How to use checksums |
b69f61c41bfac296c4b5f314e452cfda8a7bf52fe4a33f616c7c83beaaae2942
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Release files / codeorigins-0.3.1-py2.py3-none-any.whl
| Download URL | codeorigins-0.3.1-py2.py3-none-any.whl |
|---|---|
| Size | 18.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
221de229fdaba3f9d708146a48dd03473fc0df933b4d90dc5c7bc7666f183e8f
|
|
BLAKE2b-256 checksum How to use checksums |
a47040c0077a04bfa7cc38089e90386a937c6f23ee24589d779537659f9e22db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Security for codeorigins 0.3.1
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.