semvec/pypi-packages huggingface dataset:
phonexia-speech-to-text-client 2.1.1
Client for communication with Phonexia speech to text microservice.
Requires Python: >=3.9
Keywords: speech-to-text, audio, voice, speech, search, grpc

![](https://www.phonexia.com/wp-content/uploads/phonexia-logo-transparent-500px.png)
# Phonexia speech to text client

This module contains client for communication with [speech to text microservice](https://hub.docker.com/repository/docker/phonexia/speech-to-text/general) developed by [Phonexia](https://phonexia.com).

To use this client you will first need a running instance of any *Phonexia speech to text microservice*. If you don't yet have any running instance, don't hesitate to [contact our sales department](mailto:info@phonexia.com).

You can learn more about the speech to text technology [here](https://docs.phonexia.com/products/speech-platform-4/technologies/speech-to-text/).

On [this page](https://docs.phonexia.com/products/speech-platform-4/grpc/api/phonexia/grpc/technologies/speech_to_text/v1/speech_to_text.proto), you will find a *gRPC API* reference for *speech to text microservice*.
royal-mail-click-and-drop 0.0.10
Royal Mail Click and Drop Client
Requires Python: >=3.12

A basic client for interacting with the Royal Mail Click and Drop API.

Most of the code is auto generated by OpenAPI Generator from the OpenAPI spec available at https://api.parcel.royalmail.com/.

However the generated code is verbose and not very user friendly, so this package provides a simplified client interface, as well as some normalisation to work with [Shipaw](https://github.com/pawrequest/shipaw/tree/v3).

See [Generated README](README_AUTO.md)

NOTE: This package is in early development and the API is subject to change.
swh.search 0.23.0
Software Heritage search service
Requires Python: >=3.9

Software Heritage - Search service
==================================

Search service for the Software Heritage archive.

It is similar to swh-storage in what it contains, but provides different ways
to query it: while swh-storage is mostly a key-value store that returns an
object from a primary key, swh-search is focused on reverse indices, to allow
finding objects that match some criteria; for example full-text search.

Currently uses ElasticSearch, and provides only origin search (by URL and
metadata).

Dependencies
------------

- Python tests for this module include tests that cannot be run without a local
  ElasticSearch instance, so you need the ElasticSearch server executable on
  your machine (no need to have a running ElasticSearch server).

  - Debian-like host

    The elasticsearch package is required. As it's not part of debian-stable,
    `another debian repository is required to be configured`_

    .. _`another debian repository is required to be configured`: https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html

  - Non Debian-like host

    The tests expect:

    - ``/usr/share/elasticsearch/jdk/bin/java`` to exist.
    - ``org.elasticsearch.bootstrap.Elasticsearch`` to be in java's classpath.

- Emscripten is required for generating tree-sitter WASM module. The following
  commands need to be executed for the setup:

  .. code-block:: shell

     cd /opt && git clone https://github.com/emscripten-core/emsdk.git && cd emsdk && \
     ./emsdk install latest && ./emsdk activate latest
     PATH="${PATH}:/opt/emsdk/upstream/emscripten"


  **Note:** If emsdk isn't found in the PATH, the tree-sitter cli automatically pulls `emscripten/emsdk` image from docker hub when `make ts-build-wasm` or `make ts-build` is used.


Make targets
------------

Below is the list of available make targets that can be executed from the root
directory of swh-search in order to build and/or execute the swh-search under
various configurations:

* **ts-install**: Install node_modules and emscripten SDK required for
  TreeSitter

* **ts-generate**: Generate parser files(C and JSON) from the grammar

* **ts-repl**: Starts a web based playground for the TreeSitter grammar. It's
  the recommended way for developing TreeSitter grammar.

* **ts-dev**: Parse the `query_language/sample_query` and print the
  corresponding syntax expression along with the start and end positions of all
  the nodes.

* **ts-dev sanitize=1**: Same as **ts-dev** but without start and end position
  of the nodes. This format is expected by TreeSitter's native test command.
  `sanitize=1` cleans the output of **ts-dev** using `sed` to achieve the
  desired format.

* **ts-test**: executes TreeSitter's native tests

* **ts-build-so**: Generates `swh_ql.so` file from the previously generated
  parser using py-tree-sitter

* **ts-build-so**: Generates `swh_ql.wasm` file from the previously generated
  parser using emscripten

* **ts-build**: Executes both **ts-build-so** and **ts-build-so**
nikki-utils 0.0.14
Simple utils I use across many of my Python projects
Requires Python: >=3.10

# nikki-utils
[![PyPI version](https://img.shields.io/pypi/v/nikki-utils)](https://pypi.org/project/nikki-utils/)
![License](https://img.shields.io/pypi/l/nikki-utils?cacheSeconds=0)
![Python versions](https://img.shields.io/pypi/pyversions/nikki-utils)

A set of utils for me to use across multiple Python projects.
umodl 0.0.28
A 'subprocess.run' wrapper around the umodl program
Requires Python: >=3.9

<img src=https://github.com/khiopsML/khiops/blob/dev/packaging/common/images/khiops.png width=60 />

# UModl
This repository contains:
- UModl, a C++ program forked from Khiops
- umodl, a Python wrapper around the C++ program.

## About the Python wrapper
The Python wrapper is a Python package that, when built, compiles the C++ program.
It also contains [a bit of Python code](./src/umodl) exporting a single function that runs the
compiled C++ program as a subprocess.

Besides the files needed for the compilation of the C++ program, the list of the files composing
the Python wrapper is the following:
- [./README.md](./README.md) (this file)
- [./LICENSE](./LICENSE)
- [./pyproject.toml](./pyproject.toml)
- [./packaging/python/umodl/\_\_init__.py](./packaging/python/umodl/__init__.py)
- [./packaging/python/umodl/runumodl.py](./packaging/python/umodl/runumodl.py)

The build backend of the wrapper is **scikit-build-core**.

# Khiops
Khiops is an AutoML suite for supervised and unsupervised learning

## Installation
For the installation instructions [go to Khiops website][khiops-web].

## Documentation
See the documentation [at the Khiops website][khiops-web]

## Development
See the [developer's documentation wiki][wiki-dev].

## License
This software is distributed under the BSD 3-Clause-clear License, the text of which is available at
https://spdx.org/licenses/BSD-3-Clause-Clear.html or see the [LICENSE](./LICENSE) for more
details.

## Help Contact
khiops.team@orange.com


[khiops-web]: https://khiops.org
[wiki-dev]: https://github.com/KhiopsML/khiops/wiki
muuk-maintenance 0.1.3
MCP server for analyzing and repairing E2E test failures
Requires Python: >=3.10
Keywords: mcp, testing, playwright, e2e, test-repair, ai, automation, muuktest, maintenance

# MuukTest Maintenance MCP

MCP server for analyzing and repairing E2E test failures (Playwright, Cypress, Selenium, etc).

## Requirements

- Python 3.10+
- [uv](https://github.com/astral-sh/uv)

## Configuration

### VS Code / GitHub Copilot

Open User MCP Configuration (`Cmd+Shift+P` → "MCP: Open User Configuration"):

```json
{
  "inputs": [
    {
      "id": "muuk_key",
      "type": "promptString",
      "description": "Muuk Key available at MuukTest account",
      "password": true
    }
  ],
  "servers": {
    "muuk-maintenance": {
      "command": "uvx",
      "args": ["muuk-maintenance"],
      "env": {
        "MUUK_KEY": "${input:muuk_key}"
      }
    }
  }
}
```

### Claude Desktop

Edit `~/.config/claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "muuk-maintenance": {
      "command": "uvx",
      "args": ["muuk-maintenance"],
      "env": {
        "MUUK_KEY": "your-api-key"
      }
    }
  }
}
```

## Usage

Ask your AI agent:

```
Analyze the test failure in my project.
The test files are in ./test-files/ and failure data is in ./failure-data/
```

## Required Parameters

| Parameter | Description |
|-----------|-------------|
| `workspace_path` | Absolute path to project root (agent provides this automatically) |
| `test_files_path` | Path to test files directory |
| `failure_data_path` | Path to failure data directory |

## Environment Variables

| Variable | Description |
|----------|-------------|
| `MUUK_KEY` | Your MuukTest key |

## Available AI Presets

- `claude` (default)
- `openai`
- `gemini`

## Troubleshooting

### "The command uvx needed to run muuk-maintenance was not found"

VS Code can't find `uvx` in the PATH. Run in terminal:

```bash
which uvx
```

Then add the path to your shell profile (`~/.zshrc` or `~/.bashrc`):

```bash
export PATH="$PATH:/path/from/which/uvx"
```

Restart VS Code after making changes.