semvec/pypi-packages huggingface dataset:
reproducibly 0.0.20
Reproducibly build Python packages.
Requires Python: >=3.13

# reproducibly.py

## Introduction / Reproducibly build Python packages.

This project is a convenient wrapper around [build] and [cibuildwheel] that sets
metadata like file modification times, user and group IDs and names, and file
permissions predictably. The code can be used from PyPI or as a single [file]
with [inline script metadata].

## Usage

Command to run from PyPI and view help:

    pipx run reproducibly --help

Command to run from a local file and view help:

    pipx run ./reproducibly.py --help

Output:

<!--[[[cog
from subprocess import run

import cog

CMD = ".venv/bin/python ./reproducibly.py --help"

cog.out("\n")
cog.out("```\n")
cog.out(run(CMD.split(), text=True, check=True, capture_output=True).stdout)
cog.out("```\n")
cog.out("\n")
]]]-->

```
usage: reproducibly.py [-h] [--version] input [input ...] output

Reproducibly build Python packages.

features:

- Builds a source distribution (sdist) from a git repository
- Builds a wheel from a sdist
- Resets metadata like user and group names and ids to predictable values
- Uses no compression for predictable file hashes across Linux distributions
- By default uses the last commit date and time from git
- Respects SOURCE_DATE_EPOCH when building a sdist
- Single file script with inline script metadata or PyPI package

positional arguments:
  input       Input git repository or source distribution
  output      Output directory

options:
  -h, --help  show this help message and exit
  --version   show program's version number and exit
```

<!--[[[end]]]-->

## Development

This project uses [Nox](https://nox.thea.codes/en/stable/).

Builds are run every day to check for reproducibility: <br />
[![status](https://github.com/maxwell-k/reproducibly/actions/workflows/nox.yaml/badge.svg?event=schedule)](https://github.com/maxwell-k/reproducibly/actions?query=event:schedule)

To set up a development environment use:

    nox --session=dev

To run unit tests and integration tests:

    nox

[build]: https://pypi.org/project/build/
[cibuildwheel]: https://pypi.org/project/cibuildwheel/
[file]: https://github.com/maxwell-k/reproducibly/blob/main/reproducibly.py
[inline script metadata]: https://packaging.python.org/en/latest/specifications/inline-script-metadata/

<!--
README.md
Copyright 2023 Keith Maxwell
SPDX-License-Identifier: CC-BY-SA-4.0

vim: set filetype=markdown.dprint.cog.htmlCommentNoSpell :
-->
pyproject-tmpl 0.1.1.dev11
template python project with necessary configurations
Requires Python: >=3.10

# pyproject-tmpl

## features

1. pytest
2. pre-commit
3. darker for code format
4. ruff for lint
5. commitlint for commit message format
6. typer for cli
7. sqlmodel for database ORM
8. alembic for database migration

## introduction

the project uses `src-layout`, includes `my_sdk` (for publish) and `biz` (for business logic).

~~`sdk` is designed for publish and no need to rename, we use file/folder mapping `my_sdk=src/sdk` in `pyproject.toml`.~~

feel free to rename `my_sdk` to `[the name you want]` in the whole project for your own use or publish.

### dev

before you start:

1. must run `./scripts/setup`
1. replace `my_sdk` with `[the name you want]` in the whole project
1. ~~remember to `uv pip install -e .[all]` to make sure `my_sdk` is available in development.~~

### unit test

`uv run -m pytest`

### run cli

`uv run main.py --help`

### release sdk

1. `cp .pypirc.example .pypirc`
2. replace your token in `.pypirc`
3. `git tag vx.y.z`
4. `./scripts/publish`

### build executable file

`./scripts/build`
inye-adk 0.2.0
Inye Agentic Development Kit - Intent clarification command for Claude Code
Requires Python: >=3.10
Keywords: adk, agent, ai, claude, claude-code, intent

# Inye-ADK

**Inye Agentic Development Kit** - Intent clarification command for Claude Code.

## What is this?

Inye-ADK provides the `/inye:intent` command for Claude Code that forces exhaustive questioning until user intent converges to a single unambiguous requirement.

**The problem:** AI typically picks the most probable interpretation and runs with it.

**The solution:** `/inye:intent` makes AI ask questions until there's only ONE possible interpretation.

## Installation

```bash
# Using pipx (recommended)
pipx install inye-adk

# Using uv
uv tool install inye-adk

# Using pip
pip install inye-adk
```

## Usage

### Initialize in your project

```bash
cd your-project
inye init
```

This installs the `/inye:intent` command to `.claude/commands/inye/`.

### Use in Claude Code

```
/inye:intent Add order cancellation feature
```

Claude will then ask high-level questions until your intent is 100% clear:

1. "What's the main reason users need to cancel orders?"
2. "Can all orders be cancelled, or only before shipping?"
3. "What happens to payment when cancelled?"
4. ...continues until clear...

Then presents a summary for your confirmation:

```
Based on our discussion:

**Purpose:**
Allow users to self-cancel orders before shipping...

**Scope:**
- Included: Full order cancellation, auto-refund
- Excluded: Partial cancellation

**Success Criteria:**
- User can cancel from order detail page
- Refund is automatically initiated

Is this correct?
```

## MoAI Compatibility

Inye-ADK is compatible with [MoAI-ADK](https://github.com/modu-ai/moai-adk). When `.moai/project/` files exist:

- `product.md` - Product definition
- `structure.md` - Project structure
- `tech.md` - Tech stack

The `/inye:intent` command reads these files to ask more contextual questions.

## Commands

| Command | Description |
|---------|-------------|
| `inye init` | Install /inye:intent command in current project |
| `inye status` | Check if /inye:intent command is installed |

## License

MIT
booster-robotics-sdk-python 1.1.1
Booster Robotics SDK Python bindings and examples.
Requires Python: >=3.10

# Booster Robotics SDK
Booster Robotics SDK aims to provide a simple and easy-to-use interface for developers to control the Booster Robotics products. 

## Prebuild environment
* OS  (Ubuntu 22.04 LTS)  
* CPU  (aarch64 and x86_64)   
* Compiler  (gcc version 11.4.0) 

## Installation
```bash
pip3 install pybind11
# pip3 install pybind11-stubgen
```

## Build examples
```bash
mkdir build
cd build
cmake ..
make
```

## Build python binding api and install
```bash
mkdir build
cd build
cmake .. -DBUILD_PYTHON_BINDING=on
make
sudo make install

if pybind11-stubgen cannot be found even after pip install, export PATH
```bash
export PATH=/home/[user name]/.local/bin:$PATH
```