OBC, the Open Badges Client
obc is a python library that provides a standard API to interact with Open
Badge platforms.
Quick start guide
Install OBC
obc is distributed as a python package. It can be installed using pip (or
any other package manager) from PyPI:
$ pip install obc
Use providers in your application
Let say you want to issue an existing Open Badge Factory badge for a list of recipients, an example implementation would look like:
from obc.providers.obf import BadgeIssue, BadgeQuery, OBF
# Configure Open Badge Factory provider using your client identifier and secret
# key
obf = OBF(client_id="my_obf_client_id", client_secret="super_secret")
# Get the badge with the "badge_id" identifier
badge = await anext(obf.badges.read(query=BadgeQuery(id="badge_id")))
# We want to issue a badge for the following recipients
issue = BadgeIssue(
recipient=[
"jane@example.org",
"tarzan@example.org"
]
)
issue = await obf.badges.issue(badge, issue)
More details will follow in the upcoming documentation.
Hack on the project
If you want to start contributing on the project, use the bootstrap Makefile
target to build the Docker development image:
$ make bootstrap
To run tests, type:
$ make test
And to lint sources, there is also a command for that:
$ make lint
If you had new dependencies to the project, you will have to rebuild the Docker image (and the development environment):
$ make build && make dev
You can explore all other target using:
$ make help
Contributing
This project is intended to be community-driven, so please, do not hesitate to get in touch if you have any question related to our implementation or design decisions.
We try to raise our code quality standards and expect contributors to follow the recommandations from our handbook.
License
This work is released under the MIT License (see LICENSE).
Metadata
Release files for obc 2.1.0
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 |
|---|---|---|---|---|
| obc-2.1.0.tar.gz | 10.5 kB | Without provenance | Details for obc-2.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| obc-2.1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for obc-2.1.0-py2.py3-none-any.whl |
Total release size: 20.1 kB
Release files / obc-2.1.0.tar.gz
| Download URL | obc-2.1.0.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6cc4354f564e2fa5ddef8d49608ea3854d5e88cf4c1356bf5d0bf7f7438d708b
|
|
BLAKE2b-256 checksum How to use checksums |
76949d6150d8a80bc8969d67c01e8c2980a8ca689f5c6d0310a02bc5c1242d84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Release files / obc-2.1.0-py2.py3-none-any.whl
| Download URL | obc-2.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
5d2725ec50b4ae81dec38309344741c7a904dfa807d99f75df972c28956f8593
|
|
BLAKE2b-256 checksum How to use checksums |
60d2b775ca14e11864da1181273ca4185c2c3aa087eab7bc20eed7e9db8d49b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Security for obc 2.1.0
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.