Skip to main content

ansys-api-sherlock gRPC Interface Package

This Python package contains the auto-generated gRPC Python interface files for Sherlock.

Installation

Provided that wheels have been published to public PyPI, you can install the latest package with this command:

pip install ansys-api-sherlock

Otherwise, in the PySherlock documentation, see the instructions for downloading and installing this package inInstall packages <https://sherlock.docs.pyansys.com/version/dev/getting_started/installation.html>_.

Build packages

To build the gRPC packages, run these commands:

pip install build
python -m build

The preceding commands create both the source distribution containing only the PROTO files and the wheel containing the PROTO files and build Python interface files.

Note that the interface files are identical regardless of the version of Python used to generate them, but the last pre-built wheel for grpcio~=1.17 was Python 3.7. To improve your build time, use Python 3.7 when building the wheel.

Manual deployment

After building the packages, manually deploy them with these commands:

pip install twine
twine upload dist/*

Note that this is automatically done through CI/CD.

Automatic deployment

This repository contains a .github directory with the ci.yml workflow file. This file uses GitHub Actions to automatically build the source and wheel packages for these gRPC Python interface files. By default, these are built on PRs, the main branch, and on tags when pushing. Artifacts are uploaded for each PR.

To publicly release wheels to PyPI, ensure that your branch is up to date and then push tags. For example, to push tags for version v0.5.0, you would use these commands:

git tag v0.5.0
git push --tags

Metadata

Release files for ansys-api-sherlock 2.3.1

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

Source distribution (sdist)

Source distribution for ansys-api-sherlock 2.3.1
File Size Uploaded Provenance Actions
ansys_api_sherlock-2.3.1.tar.gz 38.1 kB With provenance Details for ansys_api_sherlock-2.3.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ansys-api-sherlock 2.3.1
File Interpreter ABI Platform Actions
ansys_api_sherlock-2.3.1-py3-none-any.whl Python 3 none any Details for ansys_api_sherlock-2.3.1-py3-none-any.whl

Total release size: 219.3 kB

Release files / ansys_api_sherlock-2.3.1.tar.gz

Download URL ansys_api_sherlock-2.3.1.tar.gz
Size 38.1 kB
Tags Source
SHA-256 checksum
How to use checksums
296a1e67362a605fbb756f5be3a2d09dd0b70dedb6fa24aaf7694b3af48b86c7
BLAKE2b-256 checksum
How to use checksums
df652378d80f84a473eeb65329b36a9a54b7568b773f1add600427cbe0c86f1b
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 12, 2026.

Transparency log

Release files / ansys_api_sherlock-2.3.1-py3-none-any.whl

Download URL ansys_api_sherlock-2.3.1-py3-none-any.whl
Size 181.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d2358bf2d0251d9dffcf3819e46f4d95866500f0a5798d9ff761fa796a1ddd37
BLAKE2b-256 checksum
How to use checksums
2144ecfc64661085bb9c9707130707d0c64c3c80f6bdf4d32b05e9a17cf34653
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 12, 2026.

Transparency log

Security for ansys-api-sherlock 2.3.1

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 ansys_api_sherlock-2.3.1.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 12, 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

2.3.1 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