semvec/pypi-packages huggingface dataset:
ask-video 0.2.0
A CLI tool to chat with YouTube and Bilibili videos using AI.
License: MIT
Requires Python: >=3.12

# Ask Video

A tool to chat with YouTube and Bilibili videos using AI.

## Features

![demo](https://cdn.sa.net/2025/11/24/eszhMwAQBPgE8Nf.webp)

- **Video Download**: Automatically fetches video from YouTube and Bilibili videos.
- **AI Chat**: Uses OpenAI (or compatible) models to answer questions based on the video content.
- **Streaming Output**: Responses are streamed in real-time for a better user experience.
- **Cross-Platform**: Works on macOS, Linux, and Windows.

## Usage

You can run this tool directly using `uvx` without installing it manually.

### Prerequisites

You need to have [uv](https://github.com/astral-sh/uv) installed.

### Running the Tool

1.  **Set your OpenAI API Key**:
    You need to provide your OpenAI API key. You can do this by setting an environment variable.

    ```bash
    export OPENAI_API_KEY=your_api_key_here
    ```

    If you are using a custom OpenAI-compatible provider (like DeepSeek, Moonshot, etc.), you can also set the base URL and model:

    ```bash
    export OPENAI_BASE_URL=https://api.example.com/v1
    export OPENAI_MODEL_ID=gpt-5-mini-2025-08-07
    ```

2.  **Run with `uvx`**:

    ```bash
    uvx ask-video <VIDEO_URL>
    ```

    Example:

    ```bash
    uvx ask-video https://www.youtube.com/watch?v=qjPH9njnaVU
    ```

## Development

To develop or contribute to this project:

1.  **Clone the repository**:

    ```bash
    git clone https://github.com/jtsang4/ask-video.git
    cd ask-video
    ```

2.  **Install dependencies**:

    ```bash
    uv sync
    ```

3.  **Run locally**:
    ```bash
    uv run ask-video <URL>
    ```

## License

This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details.
devpath 0.1.2
A zero-config Python development hook for instantaneous package importing during development.
License: MIT
Requires Python: >=3.8
Keywords: development, packaging, sys-path, editable-install

# 🎣 devpath: The Zero-Config Python Development Hook

**devpath** is a minimal, ultra-efficient utility designed to eliminate development friction when testing Python packages. It provides an instant, self-configuring "editable install" experience without requiring external command-line tools like `pip install -e .` or complex environments.

## ✨ Philosophy: Install-and-Go Debugging

The primary goal of **devpath** is to ensure that code changes made in your source files are **immediately available** upon `import`. This is achieved by leveraging a core Python mechanism to prioritize your development directory over the installed package.

**Forget the console commands—just import and develop.**

## ⚙️ How It Works: The `sys.path` Injection (Direct Import)

The core of `devpath` is a single, concise function executed upon module import.

1.  **Automatic Detection:** When you run `import devpath`, the logic automatically searches upwards from the execution directory for the local development folder (named **`paks_repo`**).
2.  **Path Hook:** It injects the path to your source folder into the beginning of the Python's global **`sys.path`** list.
3.  **Priority:** Because the source folder is now a top-level location, all subsequent imports (e.g., `import pak1`) will find and load the **source code version** (the one you are currently editing) instead of the installed package version.

### Benefits

* **Zero Configuration:** No `pip install -e .` necessary in your workflow.
* **Instant Updates:** Code changes are reflected immediately on re-execution.
* **Minimal Footprint:** The entire library is one file (`__init__.py`).

## 🚀 Usage

### 1. Installation

Install the hook once in your development environment:

```bash
pip install devpath


📦 Proyect_folder/ (The project root)
├── 📝 my_test_script.py  <-- Your test script that runs the code.
|
└── 📁 packs_repo/         <-- Your SOURCE CODE that you edit.
    ├── 📦 pak1/           <-- Your package (e.g., your library code).
    │   ├── __init__.py
    │   └── code.py
    │
    └── 📦 pak2/
        └── ... (Other packages in development)

``` bash
import devpath             <-- The hook is now activated.
import pak1   <-- Loads 'pak1' from your source folder (libtest/pak1/)

pak1.run_my_new_feature()
# ... Modify pak1/code.py and run the script again—the new code is instantly loaded.
octodns-transip 1.0.1
Transip DNS provider for octoDNS
License: MIT
Requires Python: >=3.9

## Transip DNS provider for octoDNS

An [octoDNS](https://github.com/octodns/octodns/) provider that targets [Transip DNS](https://www.transip.eu/knowledgebase/entry/155-dns-and-nameservers/).

### Installation

#### Command line

```
pip install octodns-transip
```

#### requirements.txt/setup.py

Pinning specific versions or SHAs is recommended to avoid unplanned upgrades.

##### Versions

```
# Start with the latest versions and don't just copy what's here
octodns==0.9.14
octodns-transip==0.0.1
```

##### SHAs

```
# Start with the latest/specific versions and don't just copy what's here
-e git+https://git@github.com/octodns/octodns.git@9da19749e28f68407a1c246dfdf65663cdc1c422#egg=octodns
-e git+https://git@github.com/octodns/octodns-transip.git@ec9661f8b335241ae4746eea467a8509205e6a30#egg=octodns_transip
```

### Configuration

```yaml
providers:
  transip:
    class: octodns_transip.TransipProvider
    # Your Transip account name (required)
    account: env/TRANSIP_ACCOUNT
    # Path to a private key file (required if key is not used)
    key_file: /path/to/file
    # The api key as string (required if key_file is not used)
    #key: env/TRANSIP_KEY
    #    -----BEGIN PRIVATE KEY-----
    #    ...
    #    -----END PRIVATE KEY-----
    # if both `key_file` and `key` are presented `key_file` is used
```

### Support Information

#### Records

TransipProvider A, AAAA, ALIAS, CAA, CNAME, DS, MX, NAPTR, NS, SPF, SRV, SSHFP, TLSA, TXT

#### Root NS records

TransipProvider support root NS record management.   
**notes:** 
  - Transip currently only supports FQDN values for root nameservers.
  - Transip has no TTL for root nameservers, so the TTL value from the source is ignored 


#### Dynamic

TransipProvider does not support dynamic records.

### Development

See the [/script/](/script/) directory for some tools to help with the development process. They generally follow the [Script to rule them all](https://github.com/github/scripts-to-rule-them-all) pattern. Most useful is `./script/bootstrap` which will create a venv and install both the runtime and development related requirements. It will also hook up a pre-commit hook that covers most of what's run by CI.
ismoiloff 0.1.0
System acces to ISMOILOFF's codes
License: MIT
Requires Python: >=3.8

# ismoiloff

**OGSTH system access module with machine-code authentication**  

`ismoiloff` is a Python library that allows you to securely access OGSTH remote code system to the ISMOILOFF's code base. Designed for CLI and programmatic use.

---

## Features

- Using ismoiloff's codes without a lot troubles
- ISMOILOFF ning kodlarini ishlatish.

---

## Installation

You can install via **pip**:

```bash
pip install ismoiloff