Skip to main content

LARA Django Material - gRPC API

This directory contains the gRPC interface for the lara-django-material application, providing a high-performance API for experimental material handling in the LARA database.

Overview

The gRPC API provides remote procedure call access to the LARA Django Material service with support for multiple programming languages through protocol buffer definitions. It also contains a high-level Python interface for easy integration with Python applications.

Package: lara-django-material-grpc Python Requirement: 3.13.*

Project Structure

api/grpc/
├── go/                          # Go gRPC client code
├── connect-es/                  # Connect-ES client code
├── connectrpc-es/               # ConnectRPC ES implementations
├── grpc-web/                    # gRPC-Web client code
├── gen/                         # Generated code from protobuf definitions
├── dist/                        # Distribution packages
├── pyproject.toml               # Python project configuration
└── python/                      # Python API module root
    └── lara_django_material_grpc/
        ├── lara_django_material_data_model.py    # Data model definitions
        ├── lara_django_material_interface.py     # High-level interface
        ├── filter_search.py                     # Filter and search capabilities
        └── v1/
            └── *_pb2.py         # Generated protocol buffer code

Installation

Using uv (Recommended)

Install the lara-django-material-grpc package with uv for faster dependency resolution:

cd api/grpc
uv pip install .

Or with development dependencies:

uv pip install -e ".[dev]"

For development, install with editable mode and all dependency groups:

cd api/grpc
uv sync --all-groups

Using pip

Alternatively, install with pip:

pip install lara-django-material-grpc

Or from the local directory:

cd api/grpc
pip install .

Dependencies

  • Runtime: grpcio>=1.73.0
  • Development:
    • grpcio-tools>=1.73.0
    • pytest>=8,<9
    • pytest-cov>=6,<7
    • pytest-asyncio

Code Generation

Protocol buffer definitions are located in ../proto/lara_django_material_grpc/. To regenerate gRPC code from protobuf definitions, e.g. in case you changed the .proto file, use the Buf CLI:

cd api
buf generate

This will generate code for multiple targets as configured in buf.gen.yaml:

  • Python
  • Go
  • JavaScript/TypeScript (Connect-ES, ConnectRPC, gRPC-Web)

Running Tests

The test suite is located in api/tests/ and includes tests for all major functionalities:

Using uv

# From the api/grpc directory
uv run pytest api/tests/

# With coverage
uv run pytest api/tests/ --cov

Using pytest directly

# From the api/grpc directory
pytest api/tests/

# With coverage
pytest api/tests/ --cov

Usage Examples

Python Client

import grpc
from lara_django_material_grpc import material_pb2, material_pb2_grpc

# Create a channel to the gRPC server
channel = grpc.insecure_channel('localhost:50051')

# Create a stub (client)
stub = material_pb2_grpc.MaterialServiceStub(channel)

# Make a request
response = stub.GetMaterial(material_pb2.GetMaterialRequest(id=1))
print(response)

# Don't forget to close the channel when done
channel.close()

For more comprehensive examples, see the demo clients in `../../ python -m build


### Working with uv

This project is configured for uv with the following features:

- **Build Backend:** `uv_build>=0.9.0,<=0.10.0`
- **Module Root:** `python/` (all Python gRPC code should be placed here)
- **Dependency Groups:** Development dependencies are organized in groups

#### Common uv commands:

```bash
# Sync dependencies
uv sync

# Sync with development dependencies
uv sync --all-groups

# Add a new dependency
uv add package-name

# Add a development dependency
uv add --dev package-name

# Run a command in the uv environment
uv run python script.py

# Build the package
uv build

Module Root

The Python module root is configured at python/, meaning all Python gRPC code should be placed in that directory.

Documentation

Protocol Buffer Linting

The project uses Buf for linting and breaking change detection. Configuration is in ../buf.yaml:

  • Follows DEFAULT lint rules with specific exceptions
  • Breaking change detection enabled
  • Ignores certain Google type definitions

Contributing

Contributions are welcome! Please see the CONTRIBUTING.md file in the project root for guidelines.

When modifying protobuf definitions:

  1. Edit .proto files in ../proto/lara_django_material_grpc/
  2. Run buf generate to regenerate code
  3. Update tests as needed
  4. Run the test suite to ensure compatibility

License

See the LICENSE file in the project root.

Metadata

Release files for lara-django-material-grpc 0.2.107

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

Source distribution (sdist)

Source distribution for lara-django-material-grpc 0.2.107
File Size Uploaded Provenance Actions
lara_django_material_grpc-0.2.107.tar.gz 54.3 kB Without provenance Details for lara_django_material_grpc-0.2.107.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for lara-django-material-grpc 0.2.107
File Interpreter ABI Platform Actions
lara_django_material_grpc-0.2.107-py3-none-any.whl Python 3 none any Details for lara_django_material_grpc-0.2.107-py3-none-any.whl

Total release size: 110.3 kB

Release files / lara_django_material_grpc-0.2.107.tar.gz

Download URL lara_django_material_grpc-0.2.107.tar.gz
Size 54.3 kB
Tags Source
SHA-256 checksum
How to use checksums
09c36c3d9c929c62d94fafac4b25513f48ffe1882e2d737d189f007f02d7c7ca
BLAKE2b-256 checksum
How to use checksums
1751bf419f2014cdc2eb041058c510ca048bed391236eefbb31d6f203661fbad
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.2.0 CPython/3.13.12

Release files / lara_django_material_grpc-0.2.107-py3-none-any.whl

Download URL lara_django_material_grpc-0.2.107-py3-none-any.whl
Size 56.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
164f4cffef2f4f7af81e51929e28cdad23f7818f871f31b2e64e6c472b8087a5
BLAKE2b-256 checksum
How to use checksums
259d4319f55510dfaa6a03dc2e7631386c2d404bc21b7266e32dfc78cfdbff80
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.2.0 CPython/3.13.12

Security for lara-django-material-grpc 0.2.107

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.

Release history Release notifications | RSS feed

This release

0.2.107 This release

2 release files No 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