semvec/pypi-packages huggingface dataset:
netzooe-eservice-api 1.0.0b2
A Python wrapper for the unofficial Netz Oberösterreich eService-Portal API.
Requires Python: >=3.13
Keywords: api, component, custom component, custom integration, netzooe, eservice, hacs-component, hacs-integration, hacs-repository, hacs, hass, home assistant, home-assistant, homeassistant, integration

# Netz OÖ eService API

A Python wrapper for the unofficial Netz Oberösterreich eService-Portal API.

![coverage-badge](https://raw.githubusercontent.com/superbox-dev/netzooe_eservice_api/main/coverage-badge.svg)
[![Version](https://img.shields.io/pypi/pyversions/netzooe-eservice-api.svg)][pypi-version]
[![CI](https://github.com/superbox-dev/netzooe_eservice_api/actions/workflows/ci.yml/badge.svg?branch=main)][workflow-ci]

[pypi-version]: https://pypi.python.org/pypi//netzooe-eservice-api
[workflow-ci]: https://github.com/superbox-dev/netzooe_eservice_api/actions/workflows/ci.yml

## Getting started

```bash
pip install netzooe_eservice_api
```

## Changelog

The changelog lives in the [CHANGELOG.md](https://github.com/superbox-dev/netzooe_eservice_api/blob/main/CHANGELOG.md) document.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).

## Get Involved

The **Netz OÖ eService-Portal API** is an open-source project and contributions are welcome. You can:

* Report [issues](https://github.com/superbox-dev/netzooe_eservice_api/issues/new/choose) or request new features
* Improve documentation
* Contribute code
* Support the project by starring it on GitHub ⭐

I'm happy about your contributions to the project!
You can get started by reading the [CONTRIBUTING.md](https://github.com/superbox-dev/netzooe_eservice_api/blob/main/CONTRIBUTING.md).
linkml-runtime 1.10.0rc5
Runtime environment for LinkML, the Linked open data modeling language
Requires Python: >=3.10
Keywords: linkml, metamodel, owl, rdf, schema visualization, yaml

# linkml-runtime
[![Pyversions](https://img.shields.io/pypi/pyversions/linkml-runtime.svg)](https://pypi.python.org/pypi/linkml-runtime)
![](https://github.com/linkml/linkml-runtime/workflows/Build/badge.svg)
[![badge](https://img.shields.io/badge/launch-binder-579ACA.svg)](https://mybinder.org/v2/gh/linkml/linkml-runtime/main?filepath=notebooks)
[![PyPi](https://img.shields.io/pypi/v/linkml-runtime.svg)](https://pypi.python.org/pypi/linkml)
[![PyPIDownloadsTotal](https://pepy.tech/badge/linkml-runtime)](https://pepy.tech/project/linkml-runtime)
[![PyPIDownloadsMonth](https://img.shields.io/pypi/dm/linkml-runtime?logo=PyPI&color=blue)](https://pypi.org/project/linkml-runtime)
[![codecov](https://codecov.io/gh/linkml/linkml-runtime/branch/main/graph/badge.svg?token=FOBHNSK5WG)](https://codecov.io/gh/linkml/linkml-runtime)

Runtime support for linkml generated data classes.

## About

This Python library provides runtime support for [LinkML](https://linkml.io/linkml/) datamodels.

See the [LinkML repo](https://github.com/linkml/linkml) for the [Python Dataclass Generator](https://linkml.io/linkml/generators/python.html) which will convert a schema into a Python object model. That model will have dependencies on functionality in this library.

The library also provides

* loaders: for loading from external formats such as json, yaml, rdf, tsv into LinkML instances
* dumpers: the reverse operation

See [working with data](https://linkml.io/linkml/data/index.html) in the documentation for more details

This repository also contains the Python dataclass representation of the [LinkML metamodel](https://github.com/linkml/linkml-model), and various utility functions that are useful for working with LinkML data and schemas.

It also includes the [SchemaView](https://linkml.io/linkml/developers/manipulating-schemas.html) class for working with LinkML schemas.

## Notebooks

See the [notebooks](https://github.com/linkml/linkml-runtime/tree/main/notebooks) folder for examples.
linkml 1.10.0rc5
Linked Open Data Modeling Language
Requires Python: >=3.10
Keywords: biolink, data modeling, linked data, owl, rdf, schema

[![Pyversions](https://img.shields.io/pypi/pyversions/linkml.svg)](https://pypi.python.org/pypi/linkml)
![](https://github.com/linkml/linkml/workflows/Build/badge.svg)
[![PyPi](https://img.shields.io/pypi/v/linkml.svg)](https://pypi.python.org/pypi/linkml)
[![badge](https://img.shields.io/badge/launch-binder-579ACA.svg)](https://mybinder.org/v2/gh/linkml/linkml/main?filepath=notebooks)
[![DOI](https://zenodo.org/badge/13996/linkml/linkml.svg)](https://zenodo.org/badge/latestdoi/13996/linkml/linkml)
[![PyPIDownloadsTotal](https://pepy.tech/badge/linkml)](https://pepy.tech/project/linkml)
[![PyPIDownloadsMonth](https://img.shields.io/pypi/dm/linkml?logo=PyPI&color=blue)](https://pypi.org/project/linkml)
[![codecov](https://codecov.io/gh/linkml/linkml/branch/main/graph/badge.svg?token=WNQNG986UN)](https://codecov.io/gh/linkml/linkml)


# LinkML - Linked Data Modeling Language

LinkML is a linked data modeling language following object-oriented and ontological principles. LinkML models are typically authored in YAML, and can be converted to other schema representation formats such as JSON or RDF.

This repo holds the tools for generating and working with LinkML. For the LinkML schema (metamodel), please see https://github.com/linkml/linkml-model

The complete documentation for LinkML can be found here:

 - [linkml.io/linkml](https://linkml.io/linkml)
svy-rs 0.3.0
Internal Rust extension for the svy package. Do not depend on this directly.
Requires Python: >=3.11

# svy-rs

> **Internal package** — This is a compiled Rust extension for the [svy](https://pypi.org/project/svy/) package. Do not depend on this directly.

## Installation

This package is automatically installed as a dependency of `svy`:

```bash
pip install svy
```

Do not install `svy-rs` directly unless you know what you're doing.
shipit-cli 0.17.5
Shipit CLI is the best way to build, serve and deploy your projects anywhere.
Requires Python: >=3.10

# Shipit

Shipit is a CLI that automatically detects the type of project you are trying to run, builds it and runs it using [Starlark](https://starlark-lang.org/) definition files (called `Shipit`).

It can run builds locally, inside Docker, or through Wasmer, and bundles a one-command experience for common frameworks.

## Quick Start

To use shipit, you'll need to have [uv](https://docs.astral.sh/uv/) installed.

Install nothing globally; use `uvx shipit-cli` to run Shipit from anywhere.

```bash
uvx shipit-cli .
```

Running in `auto` mode will generate the `Shipit` file when needed, build the project, and can
also serve it. Shipit picks the safest builder automatically and falls back to
Docker or Wasmer when requested:

- `uvx shipit-cli . --wasmer` builds locally and serves inside Wasmer.
- `uvx shipit-cli . --docker` builds it with Docker (you can customize the docker client as well, eg: `--docker-client depot`).
- `uvx shipit-cli . --start` launches the app after building.

You can combine them as needed:

```
uvx shipit-cli . --start --wasmer --skip-prepare
```

## Commands

### Default `auto` mode

Full pipeline in one command. Combine flags such as `--regenerate` to rewrite
the `Shipit` file. Use
`--wasmer` to run with Wasmer, or `--wasmer-deploy` to deploy to Wasmer Edge.

### `generate`

```bash
uvx shipit-cli generate .
```

Create or refresh the `Shipit` file. Override build and run commands with
`--install-command`, `--build-command`, or `--start-command`. Pick a exlicit provider
with `--use-provider`.

### `plan`

```bash
uvx shipit-cli plan --out plan.json
```

 Evaluate the project and emit config, derived commands, and required
services without building. Helpful for CI checks or debugging configuration.

### `build`

```bash
uvx shipit-cli build
```

Run the build steps defined in `Shipit`. Append `--wasmer` to execute inside
Wasmer, `--docker` to use Docker builds.

### `serve`

```bash
uvx shipit-cli serve
```

Execute the start command for the project. Combine with `--wasmer` for WebAssembly execution, or `--wasmer-deploy` to deploy to Wasmer Edge.

## Supported Technologies

Shipit works with three execution environments:

- Local builder for fast, host-native builds.
- Docker builder when container isolation is required.
- Wasmer runner for portable WebAssembly packaging and deployment.

## Development

Clone the repository and use the `uv` project environment.

```bash
uv run shipit . --start
```

Use any other subcommand during development by prefixing with `uv run shipit`,
for example `uv run shipit build . --wasmer`. This keeps changes local while
matching the published CLI behaviour.

### Tests

Run the test suite with:

```bash
uv run pytest
```

You can run the e2e tests in parallel (`-n 8`) with:

```bash
uv run pytest -m e2e -v "tests/test_e2e.py" -s -n 8
```

The e2e tests will:
* Build the project (locally, or with docker)
* Run the project (locally or with Wasmer)
* Test that the project output (via http requests) is the correct one