semvec/pypi-packages huggingface dataset:
corpo 0.2.0
Form and govern Wyoming DAO LLCs on Solana
Requires Python: >=3.11
Keywords: dao, governance, lao, llc, solana, wyoming

# corpo CLI

Agent-facing CLI for forming and governing Wyoming DAO LLCs on Solana.

## Install

```bash
uvx corpo          # run directly
pip install corpo  # or install
```

## Quick Start

```bash
corpo init                    # generate keypair + config
corpo status                  # show identity & realm context
corpo realms                  # list all realms
corpo proposals --governance <addr>
corpo vote --proposal <addr> --proposal-owner-record <addr> --choice approve
```

## Formation (Phase 2)

```bash
corpo form draft --name "MyDAO LLC" --members 3
corpo form file --draft-id <id>
corpo form status --filing-id <id>
corpo quote --amount 500
corpo pay --quote-id <id>
```

## Config

`~/.corpo/config.toml`:

```toml
[identity]
keypair = "~/.corpo/keypair.json"

[network]
api_url = "https://api.corpo.dev"
rpc_url = "https://api.devnet.solana.com"
program_id = "GTesTBiEWE32WHXXE2S4XbZvA5CrEc4xs6ZgRe895dP"

[defaults]
realm = ""
governance = ""
governing_token_mint = ""
```

Resolution order: CLI flag > env var (`CORPO_*`) > config.toml > built-in default.
datasette-showboat 0.1a1
Datasette plugin for SHOWBOAT_REMOTE_URL
Requires Python: >=3.10

# datasette-showboat

[![PyPI](https://img.shields.io/pypi/v/datasette-showboat.svg)](https://pypi.org/project/datasette-showboat/)
[![Changelog](https://img.shields.io/github/v/release/simonw/datasette-showboat?include_prereleases&label=changelog)](https://github.com/simonw/datasette-showboat/releases)
[![Tests](https://github.com/simonw/datasette-showboat/actions/workflows/test.yml/badge.svg)](https://github.com/simonw/datasette-showboat/actions/workflows/test.yml)
[![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://github.com/simonw/datasette-showboat/blob/main/LICENSE)

Datasette plugin that provides a remote viewer for [Showboat](https://github.com/simonw/showboat) documents. It receives streaming document chunks over HTTP and displays them in a live-updating web interface.

See [this blog post](https://simonwillison.net/2026/Feb/17/chartroom-and-datasette-showboat/#datasette-showboat) for background on this project.

## Installation

Install this plugin in the same environment as Datasette.
```bash
datasette install datasette-showboat
```

## Usage

Once installed, the plugin adds a `/-/showboat` page to your Datasette instance listing all received documents, and a `/-/showboat/receive` endpoint for ingesting chunks.

### Sending documents

Set the `SHOWBOAT_REMOTE_URL` environment variable to point at your Datasette instance:

```bash
export SHOWBOAT_REMOTE_URL="https://your-datasette-instance/-/showboat/receive"
```

The `/-/showboat` page will display the correct URL for your instance including the hostname.

### Permissions

Viewing showboat documents requires the `showboat` permission. By default this is **denied** to anonymous users — only the root user (when Datasette is started with `--root`) has access automatically.

To grant access to specific users, add to your `datasette.yaml`:

```yaml
permissions:
  showboat:
    id: your-username
```

Or to allow all authenticated users:

```yaml
permissions:
  showboat:
    id: "*"
```

The receive endpoint (`/-/showboat/receive`) does not require the `showboat` permission — it uses token authentication instead (see below).

### Token authentication

To protect the receive endpoint, configure a secret token in your `datasette.yaml` (or `metadata.yaml`):

```yaml
plugins:
  datasette-showboat:
    token: your-secret-token
```

When a token is configured, all requests to `/-/showboat/receive` must include it as a query parameter:

```bash
export SHOWBOAT_REMOTE_URL="https://your-datasette-instance/-/showboat/receive?token=your-secret-token"
```

Without a configured token, the receive endpoint accepts all POST requests.

### Custom database

By default chunks are stored in Datasette's internal database. To use a named database instead:

```yaml
plugins:
  datasette-showboat:
    database: my_database
```

## Development

To set up this plugin locally, first checkout the code. You can confirm it is available like this:
```bash
cd datasette-showboat
# Confirm the plugin is visible
uv run datasette plugins
```
To run the tests:
```bash
uv run pytest
```
unitelabs-sila 0.7.5
An un-opinionated SiLA 2 library.
Requires Python: <4.0,>=3.10
Keywords: SiLA 2, automation, connectivity, laboratory

# Unitelabs SiLA Python Library

A Python library for creating SiLA 2 clients and servers. This flexible and unopinionated library gives you everything needed to create a SiLA 2 1.1 compliant Python application. It adheres to the [SiLA 2 specification](https://sila2.gitlab.io/sila_base/) and is used by the [UniteLabs CDK](https://gitlab.com/unitelabs/cdk/python-cdk) to enable rapid development of cloud-native SiLA Servers with a code-first approach.

## Getting Started

### Prerequisites

Ensure you have Python 3.9+ installed. You can install Python from [python.org](https://www.python.org/downloads/).

### Quickstart

To get started quickly with your first connector, we recommend to use our [UniteLabs CDK](https://gitlab.com/unitelabs/cdk/python-cdk). Use [Cookiecutter](https://www.cookiecutter.io) to create your project base on our [Connector Factory](https://gitlab.com/unitelabs/cdk/connector-factory) starter template:

```
cookiecutter git@gitlab.com:unitelabs/cdk/connector-factory.git
```

### Installation

Install the latest version of the library into your Python project:

```python
pip install unitelabs-sila
```

## Usage

To start using the SiLA Python library in your project:

1. Import and configure your SiLA server instance:

    ```python
    import asyncio

    from sila.server import Server
    from your_project.features import your_feature

    async def main():
        server = Server({"port": 50000})
        server.add_feature(your_feature)
        await server.start()

    asyncio.run(main())
    ```

2. To implement a custom SiLA Feature, create a feature definition following the SiLA2 specification:

    ```python
    from sila.server import Feature, UnobservableCommand

    your_feature = Feature(...)
    your_method = UnobservableCommand(...)
    your_method.add_to_feature(your_feature)
    ```

3. Run your server:

    ```bash
    $ python your_script.py
    ```

> Important: Without implementing the required SiLA Service Feature, your SiLA Server will not be fully compliant with the standard. For easier compliance, consider using the [UniteLabs CDK](https://gitlab.com/unitelabs/cdk/python-cdk), which handles this automatically.

## Contribute

Submit and share your work!  
https://hub.unitelabs.io

We encourage you to submit feature requests and bug reports through the GitLab issue system. Please include a clear description of the issue or feature you are proposing. If you have further questions, issues, or suggestions for improvement, don't hesitate to reach out to us at [developers@unitelabs.io](mailto:developers+sila@unitelabs.io).

Join the conversation! Stay up to date with the latest developments by joining the Python channel in the [SiLA Slack](https://sila-standard.org/slack).

## License

Distributed under the MIT License. See [MIT license](LICENSE) for more information.
trikhub 0.6.0
Python SDK for TrikHub - AI skills marketplace
Requires Python: >=3.10
Keywords: ai, agents, skills, llm, tools

# TrikHub Python SDK

Python SDK for TrikHub - AI skills marketplace.

## Installation

```bash
pip install trikhub
```

## Quick Start

```python
from trikhub import TrikGateway

# Initialize the gateway
gateway = TrikGateway()
await gateway.initialize()

# Load triks from config
await gateway.load_triks_from_config()

# Get available tool definitions
tools = gateway.get_tool_definitions()
```

## CLI Usage

```bash
# Install a trik
trik install @scope/trik-name

# List installed triks
trik list

# Search for triks
trik search "topic"
```

## Documentation

For full documentation, visit [docs.trikhub.com](https://docs.trikhub.com).

## License

MIT
cryptofunc 0.1.0
Extract cryptographic functions and attributes from a codebase.
Requires Python: >=3.12

# Crypto Function Extractor

Extract cryptographic functions and attributes from a codebase.

## Usage

Legacy: `pip install cryptofunc`

Preferred: `uv add cryptofunc`

## Developing further

> Development flow as [Paleofuturistic Python](https://github.com/schubergphilis/paleofuturistic_python)

Prerequisite: [uv](https://docs.astral.sh/uv/)

### Setup

- Fork and clone this repository.
- Download additional dependencies: `uv sync --all-extras --dev`
- Optional: validate the setup with `uv run python -m unittest`

### Workflow

- Download dependencies (if you need any): `uv add some_lib_you_need`
- Develop (optional, tinker: `uvx --with-editable . ptpython`)
- QA:
    - Format: `uv run ruff format`
    - Lint: `uv run ruff check`
    - Type check: `uv run mypy`
    - Test: `uv run python -m unittest`
- Build (to validate it works): `uv build`
- Review documentation updates: `uv run mkdocs serve`
- Make a pull request.
oldp-de 0.1.3
German Theme for Open Legal Data Platform
Requires Python: >=3.11

# OLDP DE: German Theme for Open Legal Data

[![PyPI version](https://img.shields.io/pypi/v/oldp-de.svg)](https://pypi.org/project/oldp-de/)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

## Getting Started

Install from PyPI:

```bash
pip install oldp-de
```

Or install the latest development version directly from GitHub:

```bash
pip install git+https://github.com/openlegaldata/oldp-de.git
```

For local development:

```bash
git clone https://github.com/openlegaldata/oldp-de.git
cd oldp-de
pip install -e ".[dev]"
```

## Configuration

Tell OLDP to use the OLDP-DE settings file and development configuration:

```bash
export DJANGO_SETTINGS_MODULE=oldp_de.settings
export DJANGO_CONFIGURATION=DevDEConfiguration  # For production use `ProdDEConfiguration`
```

Start OLDP as always (from OLDP directory):

```bash
python manage.py runserver
```

## How does it work?

By loading another settings file, we basically just tell Django to use assets (templates, images, ...) from the German theme if they exist.
As a result, we can modify the layout etc. without touching the original OLDP code.

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
craftllc-wikin 1.2.5
A simple documentation generator for Python
Requires Python: >=3.8

# Wikin

A simple, beautiful documentation generator for Python. It extracts docstrings from functions and special comments from variables.

## Features

- **Function Docstrings**: Standard Python triple-quoted docstrings.
- **Variable Documentation**: 
  - `#: comment before variable`
  - `variable = value #: comment after variable`
- **Modern UI**: Clean, responsive HTML output with a premium look.
- **Markdown Support**: Use Markdown in your docstrings and comments.
- **Module Metadata**: Customize how modules appear in the documentation using a `Wikin:` block.

## Installation

```bash
pip install craftllc-wikin
```

## Usage

```bash
wikin <path_to_code> <project_name> <version>
```

Example:

```bash
wikin ./ "My Project" 1.0.0
```

This will generate documentation in the `docs/index.html` file.

## Variable Documentation Example

```python
#: Number of requests per second
rpm = 10

timeout = 30 #: Connection timeout in seconds
```

Wikin will pick these up and include them in the generated documentation.

## Ignoring Files

To exclude specific files or directories from being processed, create a `.wikinignore` file in your `docs/` folder. It supports standard `.gitignore` (gitwildmatch) patterns.

**Example `docs/.wikinignore`:**

```text
# Ignore a specific file
secret_module.py

# Ignore an entire directory
internal_tools/

# Ignore all files with a certain extension
*.deprecated.py
```

## Configuration

You can customize your documentation by creating a `docs/.wikinconfig` file (TOML format) in your documentation directory.

### Adding Project Links

To add helpful links (like GitHub, PyPI, or your website) to the sidebar, use the `[links]` section:

```toml
[links]
PyPI = "https://pypi.org/project/craftllc-wikin"
GitHub = "https://github.com/CraftLLC/Wikin"
```

These links will appear as stylish buttons in the sidebar for quick access.

## Module Metadata Example

You can set a custom display name for your modules by adding a `Wikin:` block at the top of your module's docstring:

```python
"""
Wikin:
    name: Core Parser

This module handles all the parsing logic for Wikin.
"""
```

In the documentation, this module will be titled as **Core Parser (your_package.parser)**. The metadata block itself will be hidden from the module's description.