Anaconda Client
This is a command line client that provides an interface to anaconda.org.
Quickstart:
First, create an account on anaconda.org, if you may still don't have one.
Then, install anaconda-client into your conda environment:
conda install anaconda-client
Log into your account:
anaconda login
Test your login wit the whoami command:
anaconda whoami
For a complete tutorial on building and uploading Conda packages to anaconda.org visit the documentation page.
For channel notices (conda user-facing messages), see doc/channel_notices.md.
Local development
Setup conda environment:
make init
Activate development environment:
conda activate anaconda_client
Run anaconda-client commands:
python -m binstar_client.scripts.cli --version
Setup conda environment for testing telemetry:
- By default this uses an editable install of
anaconda-opentelemetry- Assumes that project root is adjacent to this one
- If you don't have the repo cloned it will not work. Removing it from the environment-tel.yml file will use the a package version from conda defaults that satisfies the dependency of
anaconda-cli-base - You may also want an editable install of
anaconda-cli-basesince it is the source of telemetry export, in which case just add that to theenvironment-tel.ymlfile, remove the environment, and run make init-tel again
make init-tel
Activate it:
conda activate ./tel-env
Pre-commit Setup in Local
Pre-commit also runs in the GitHub workflow on pull requests. Installing it locally is recommended so you catch formatting and lint issues before pushing, and avoid back-and-forth commits when CI auto-fixes files. Set this up from the development environment (./env, Python 3.11) — some hooks require Python ≥ 3.10.
conda activate ./env # Need not run if anaconda-client env is already activated
pip install pre-commit
pre-commit install # wire git hooks to this env's Python
pre-commit install-hooks # download hook environments
After pre-commit install, hooks run automatically on each git commit — you do not need to run anything extra before pushing. Optionally, make pre-commit runs all hooks across the entire repo (useful before opening a PR).
If commits still fail with a Python 3.9 error, the git hook was likely installed from a different environment (for example base Miniconda). Re-install from ./env:
conda activate ./env # Need not run if anaconda-client env is already activated
pre-commit clean
pre-commit install
pre-commit install-hooks
and run git commit to commit all changes.
Metadata
Release files for anaconda-client 1.16.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 |
|---|---|---|---|---|
| anaconda_client-1.16.0.tar.gz | 778.5 kB | Without provenance | Details for anaconda_client-1.16.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| anaconda_client-1.16.0-py3-none-any.whl | Python 3 | none | any | Details for anaconda_client-1.16.0-py3-none-any.whl |
Total release size: 927.0 kB
Release files / anaconda_client-1.16.0.tar.gz
| Download URL | anaconda_client-1.16.0.tar.gz |
|---|---|
| Size | 778.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c9422edaada605306854a1d25a6395cf7c8b727fd1de843250d47f32ef45076
|
|
BLAKE2b-256 checksum How to use checksums |
60108b53d40c34cbb424bb40eb9929bed9c156d7fede3626b3288a8565ec08f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.18.1 {"ci":true,"cpu":"x86_64","distro":{"id":"noble","libc":{"lib":"glibc","version":"2.39"},"name":"Ubuntu","version":"24.04"},"implementation":{"name":"CPython","version":"3.12.3"},"installer":{"name":"hatch","version":"1.18.1"},"openssl_version":"OpenSSL 3.0.13 30 Jan 2024","python":"3.12.3","system":{"name":"Linux","release":"6.17.0-1022-azure"}} HTTPX2/2.13.1
|
Release files / anaconda_client-1.16.0-py3-none-any.whl
| Download URL | anaconda_client-1.16.0-py3-none-any.whl |
|---|---|
| Size | 148.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44d58b3b37499440baeae342e0574dc1107d2b9529d2ffc9416d8a3cb022e4c2
|
|
BLAKE2b-256 checksum How to use checksums |
7632ecfd66ae6af0a56cfd267ad563d276b61db70da8c8f6af3cdb6048d5951a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.18.1 {"ci":true,"cpu":"x86_64","distro":{"id":"noble","libc":{"lib":"glibc","version":"2.39"},"name":"Ubuntu","version":"24.04"},"implementation":{"name":"CPython","version":"3.12.3"},"installer":{"name":"hatch","version":"1.18.1"},"openssl_version":"OpenSSL 3.0.13 30 Jan 2024","python":"3.12.3","system":{"name":"Linux","release":"6.17.0-1022-azure"}} HTTPX2/2.13.1
|
Security for anaconda-client 1.16.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.