codePost Terminal Tools
The codePost Terminal Tools provides a set of tools to control your codePost course from the comfort of your terminal or shell scripts. These tools are built in Python 3.x using our codePost API Python bindings, which can also be installed from PyPi.
Installation
You can install the codePost Terminal Tools in your path using pip:
pip install --upgrade codePost-tools
Usage
To use the functions available in this library, you must have a codePost API key. As of March 2019, to retrieve a codePost API key, you must be a administrator of a course on codePost. It will then be accessible from https://codepost.io/settings.
Configuration
For convenience, it is also possible to specify a default course name, course period and codePost API key, by providing these in a configuration file. This configuration file can be called codepost-config.yaml or .codepost-config.yaml and be located in the root of the local user's home directory.
api_key: "<API KEY HERE>" # https://codepost.io/settings
course_name: "<COURSE NAME HERE>"
course_period: "<COURSE PERIOD HERE>"
Command Line Syntax
> ./upload-to-codePost --help
usage: upload-to-codePost [-h] [-api_key API_KEY] [-course_name COURSE_NAME]
[-course_period COURSE_PERIOD]
[-assignment_name ASSIGNMENT_NAME]
[-students STUDENTS] [-files FILES [FILES ...]]
[--extend] [--overwrite]
optional arguments:
-h, --help show this help message and exit
-api_key API_KEY the API key to authenticate upload
-course_name COURSE_NAME the name of the course to upload to (e.g. COS126)
-course_period COURSE_PERIOD the period of the course to upload to (e.g. S2019)
-assignment_name ASSIGNMENT_NAME the name of the assignment to upload to (e.g. Loops)
-students STUDENTS comma-separated list of student emails
-files FILES [FILES ...] comma-separated list of file paths
--extend If submission already exists, add new files to it and
replace old files if the code has changed.
--overwrite If submission already exists, overwrite it.
Related Repositories
- Princeton University has variants of this tool which integrates specifically in its Tigerfile submission platform: https://github.com/PrincetonUniversity/codePost-tools
Metadata
Release files for codePost-tools 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 | |
|---|---|---|---|---|
| codePost-tools-1.0.3.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codePost_tools-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.8 kB
Release files / codePost-tools-1.0.3.tar.gz
| Download URL | codePost-tools-1.0.3.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bfa2cfd98362d3a5a808fc7cc875ec4b4f3f9d63d28cc441a79a0bbabd23a981
|
|
BLAKE2b-256 checksum How to use checksums |
8a5dab1c65e513b64ad95f32f0b7048f61921927d55e07f896acfc2b23d3a291
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.2
|
Release files / codePost_tools-1.0.3-py3-none-any.whl
| Download URL | codePost_tools-1.0.3-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2bb8f304a832e1e775e56913b1a186f241e88cb38fb15eae59a580ba61e1e37
|
|
BLAKE2b-256 checksum How to use checksums |
478cdc31969f791493135f26b5f4f5aaea7841290b7fc897e06faf8b3b6fff77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.2
|
Security for codePost-tools 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.