TSD API Client
Transport files and directories, no limits on size or amount, resumable by default, synchronise if needed.
Install
pip3 install tsd-api-client
pip3 install tsd-api-client --upgrade # to get the latest version
tacl
Get started with tacl:
tacl --guide topics # to see all guides available
tacl --help
Set up shell completion:
# for Bash, in ~/.bashrc:
eval "$(_TACL_COMPLETE=source_bash tacl)"
# for Zsh, in ~/.zshrc:
eval "$(_TACL_COMPLETE=source_zsh tacl)"
# for Fish, in ~/.config/fish/completions/tacl.fish
eval (env _TACL_COMPLETE=source_fish tacl)
Running in a container
You can run the container like this:
$ podman run --rm -ti ghcr.io/unioslo/tsd-api-client
tacl --help, for basic help
tacl --guide topics, for extended help
The container entrypoint is tacl, meaning you can pass runtime parameters to
the ghcr.io/unioslo/tsd-api-client image as if you were running tacl on your
host.
$ podman run --rm -ti ghcr.io/unioslo/tsd-api-client --version
tacl v3.5.13
- OS/Arch: Linux/aarch64
- Python: 3.12.2
You should bind mount a writable volume to /config/tacl in the container, so
that your configuration and session data persists between separate invocation.
$ podman run --rm -ti -v $HOME/.config/tacl:/config/tacl ghcr.io/unioslo/tsd-api-client --register
Choose the API environment by typing one of the following numbers:
1 - for normal production usage
2 - for use over fx03 network
3 - for testing
4 - for Educloud normal production usage
5 - for Educloud testing
>
Likely you will also want to bind mount in another volume to upload data from or write exported data to.
$ podman run --rm -ti \
-v $HOME/.config/tacl:/config/tacl \
-v $PWD:/data \
ghcr.io/unioslo/tsd-api-client
p11 --upload /data/README.md
/data/README.md ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00
1 maintainer
Metadata
1 maintainer
Release files for tsd-api-client 3.9.6
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 | |
|---|---|---|---|---|
| tsd_api_client-3.9.6.tar.gz | 33.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tsd_api_client-3.9.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 72.0 kB
Release files / tsd_api_client-3.9.6.tar.gz
| Download URL | tsd_api_client-3.9.6.tar.gz |
|---|---|
| Size | 33.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44d3f57608c1fb55f2616bc91cd4cd9427af1294696840377a24131e939eea07
|
|
BLAKE2b-256 checksum How to use checksums |
f6930fac0f996c66d6fe823f2d8c28e40ef9dfe8b7aa66655e792a8dae61ffca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / tsd_api_client-3.9.6-py3-none-any.whl
| Download URL | tsd_api_client-3.9.6-py3-none-any.whl |
|---|---|
| Size | 38.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e501bff840e953e1bd3acb98d7bd0d2fb0a2df9bf142f7c2397975d7039b8bcd
|
|
BLAKE2b-256 checksum How to use checksums |
6c4bc424a8e9fd176d2c676725d680c3c5ea5ac56a36d2f7b18493c3d4cb1e9f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for tsd-api-client 3.9.6
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.
