Skip to main content

Receptorctl

Receptorctl is a front-end CLI and importable Python library that interacts with Receptor over its control socket interface.

Setting up nox

This project includes a nox configuration to automate tests, checks, and other functions in a reproducible way using isolated environments. Before you submit a PR, you should install nox and verify your changes.

To run make receptorctl-lint and receptorctl-test from the repository root, you must first install nox.

  1. Install nox using python3 -m pip install nox or your distribution's package manager.
  2. Run nox --list from the receptorctl directory to view available sessions.

You can run nox with no arguments to execute all checks and tests. Alternatively, you can run only certain tasks as outlined in the following sections.

By default nox sessions install pinned dependencies from pyproject.toml.

Checking changes to Receptorctl

Run the following nox sessions to check for code style and formatting issues:

  • Run all checks.

    nox -s lint
    
  • Check code style.

    nox -s check_style
    
  • Check formatting.

    nox -s check_format
    
  • Format code if the check fails.

    nox -s format
    

Running Receptorctl tests

Run the following nox sessions to test Receptorctl changes:

  • Run tests against the complete matrix of Python versions.

    nox -s tests
    
  • Run tests against a specific Python version.

    # For example, this command tests Receptorctl against Python 3.12.
    nox -s tests-3.12
    

Updating dependencies

Update dependencies using uv as follows:

  1. Add or modify packages in pyproject.toml under dependencies or optional-dependencies.

  2. Regenerate the lock file from the receptorctl directory:

    uv lock
    

The uv.lock file pins all dependencies with cryptographic hashes for reproducible installs. Commit the updated uv.lock file along with your pyproject.toml changes.

Metadata

Release files for receptorctl 1.6.10

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for receptorctl 1.6.10
File Size Uploaded Provenance Actions
receptorctl-1.6.10.tar.gz 48.5 kB With provenance Details for receptorctl-1.6.10.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for receptorctl 1.6.10
File Interpreter ABI Platform Actions
receptorctl-1.6.10-py3-none-any.whl Python 3 none any Details for receptorctl-1.6.10-py3-none-any.whl

Total release size: 59.5 kB

Release files / receptorctl-1.6.10.tar.gz

Download URL receptorctl-1.6.10.tar.gz
Size 48.5 kB
Tags Source
SHA-256 checksum
How to use checksums
360696414b76ab752dce1804fb2e61d5f2997e9c8ce473172089662cb0306aab
BLAKE2b-256 checksum
How to use checksums
73ceb05d1624a2162a1f4f067b34d69336b93d4326bfea84dd6107b7a15a9e39
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.

Transparency log

Release files / receptorctl-1.6.10-py3-none-any.whl

Download URL receptorctl-1.6.10-py3-none-any.whl
Size 11.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fdce5966c6b1d48d957c2cc8275e8706222491fcfae16a597351204cd066116c
BLAKE2b-256 checksum
How to use checksums
ddf2707b5f5b266c39349c14b61243af8384a96ddb3d8d049545d916fb909e5f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.

Transparency log

Security for receptorctl 1.6.10

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for receptorctl-1.6.10.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

1.6.10 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page