semvec/pypi-packages huggingface dataset:
targetcli 3.0.2
A command shell for managing the Linux LIO kernel target
Requires Python: >=3.9

targetcli-fb
============

A command shell for managing the Linux LIO kernel target
--------------------------------------------------------
An administration shell for configuring iSCSI, FCoE, and other
SCSI targets, using the TCM/LIO kernel target subsystem. FCoE
users will also need to install and use fcoe-utils.


targetcli-fb development
------------------------
targetcli-fb is licensed under the Apache 2.0 license. Contributions are welcome.

 * Mailing list: [targetcli-fb-devel](https://lists.fedorahosted.org/mailman/listinfo/targetcli-fb-devel)
 * Source repo: [GitHub](https://github.com/open-iscsi/targetcli-fb)
 * Bugs: [GitHub](https://github.com/open-iscsi/targetcli-fb/issues) or [Trac](https://fedorahosted.org/targetcli-fb/)
 * Tarballs: [fedorahosted](https://fedorahosted.org/releases/t/a/targetcli-fb/)
 * Playlist of instructional screencast videos: [YouTube](https://www.youtube.com/playlist?list=PLC2C75481A3ABB067)

Packages
--------
targetcli-fb is packaged for a number of Linux distributions including
RHEL,
[Fedora](https://apps.fedoraproject.org/packages/targetcli),
openSUSE, Arch Linux,
[Gentoo](https://packages.gentoo.org/packages/sys-block/targetcli-fb), and
[Debian](https://tracker.debian.org/pkg/targetcli-fb).

Contribute
----------
targetcli complies with PEP 621 and as such can be built and installed with tools like `build` and `pip`.

For development, consider using [Hatch](https://hatch.pypa.io):  
`hatch shell` to create and enter a Python virtualenv with the project installed in editable mode  
`pre-commit install` to enable pre-commit hooks  
`hatch build` to create tarball and wheel  

"fb" -- "free branch"
---------------------

targetcli-fb is a fork of the "targetcli" code written by RisingTide Systems.
The "-fb" differentiates between the original and this version.
Please ensure to use either all "fb" versions of the targetcli components --
targetcli, rtslib, and configshell, or stick with all non-fb versions, since
they are no longer strictly compatible.
pytest-podman 0.0.1
Pytest plugin for Podman integration
Requires Python: >=3.10

# Pytest Podman Plugin

A Pytest plugin for managing Podman containers during tests, similar to `pytest-docker` but tailored for Podman. It simplifies integration testing by automatically starting and stopping services defined in a `podman-compose.yml` file.

## Features

- **Automatic Lifecycle Management**: Starts services (`podman compose up`) before tests and stops them (`podman compose down`) afterwards.
- **Service Discovery**: Helper methods to find the host port mapped to a container port.
- **Readiness Waiting**: Built-in mechanism to wait for services to become responsive.
- **Scoped Fixtures**: Configurable scope (default: `session`) to share containers across tests or restart them per test.

## Installation

You can install the plugin via pip:

```bash
pip install podman_pytest
```

## Usage

### 1. Create a `podman-compose.yml`

Create a `podman-compose.yml` file in your `tests/` directory (or configure the path).

```yaml
version: '3'
services:
  httpbin:
    image: kennethreitz/httpbin
    ports:
      - "80"
```
podman-pytest 0.0.1
Pytest plugin for Podman integration
Requires Python: >=3.10

# Pytest Podman Plugin

A Pytest plugin for managing Podman containers during tests, similar to `pytest-docker` but tailored for Podman. It simplifies integration testing by automatically starting and stopping services defined in a `podman-compose.yml` file.

## Features

- **Automatic Lifecycle Management**: Starts services (`podman compose up`) before tests and stops them (`podman compose down`) afterwards.
- **Service Discovery**: Helper methods to find the host port mapped to a container port.
- **Readiness Waiting**: Built-in mechanism to wait for services to become responsive.
- **Scoped Fixtures**: Configurable scope (default: `session`) to share containers across tests or restart them per test.

## Installation

You can install the plugin via pip:

```bash
pip install podman_pytest
```

## Usage

### 1. Create a `podman-compose.yml`

Create a `podman-compose.yml` file in your `tests/` directory (or configure the path).

```yaml
version: '3'
services:
  httpbin:
    image: kennethreitz/httpbin
    ports:
      - "80"
```
inquirer-textual 0.4.0
Inquirer based on Textual
Requires Python: <3.15,>=3.9

# Inquirer-Textual

<div align="center">

![Logo](https://raw.githubusercontent.com/robvanderleek/inquirer-textual/main/docs/assets/logo-light.png)

</div>

<div align="center">

  *Versatile library for user input in Python 🎙️*

</div>

<div align="center">

[![main](https://github.com/robvanderleek/inquirer-textual/actions/workflows/main.yml/badge.svg)](https://github.com/robvanderleek/inquirer-textual/actions/workflows/main.yml)
[![Checked with mypy](https://www.mypy-lang.org/static/mypy_badge.svg)](https://mypy-lang.org/)
[![Linting: Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/charliermarsh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)

</div>

All terminal programs start small. Some stay small, and some become incredibly
big. The goal of this Python library is to make user input simple for small
programs, while enabling a smooth transition to a comprehensive UI library as
your program grows.

Read the [documentation here](https://robvanderleek.github.io/inquirer-textual/)

## Installation

Create and activate a virtual environment (for example with
[uv](https://docs.astral.sh/uv/)), and then install this package:

```shell
pip install inquirer-textual
```

## Development

Add this library as an editable local dependency to another project using `uv`:

```shell
uv add --editable <path-to-inquirer-textual>
```

### Textual console

1. Open the Textual Development Console:

```shell
uv run textual console
```

2. Run application in development mode:

```shell
uv run textual run --dev examples/prompt_pattern.py
```

### Static documentation

Generating the static documentation:

```shell
uv run mkdocs build
```

Viewing the static documentation:

```shell
uv run mkdocs serve
```