semvec/pypi-packages huggingface dataset:
phonopy 2.48.0
This is the phonopy module.
Requires Python: >=3.10

[![Version Badge](https://anaconda.org/conda-forge/phonopy/badges/version.svg)](https://anaconda.org/conda-forge/phonopy)
[![Downloads Badge](https://anaconda.org/conda-forge/phonopy/badges/downloads.svg)](https://anaconda.org/conda-forge/phonopy)
[![PyPI](https://img.shields.io/pypi/dm/phonopy.svg?maxAge=2592000)](https://pypi.python.org/pypi/phonopy)
[![codecov](https://codecov.io/gh/phonopy/phonopy/branch/develop/graph/badge.svg)](https://codecov.io/gh/phonopy/phonopy)

# Phonopy

Phonon code mainly written in python. Phonopy user documentation is found at
http://phonopy.github.io/phonopy/

## Installation

See https://phonopy.github.io/phonopy/install.html.

## Mailing list for questions

Usual phonopy questions should be sent to phonopy mailing list
(https://sourceforge.net/p/phonopy/mailman/).

## Development

The development of phonopy is managed on the `develop` branch of github phonopy
repository.

- Github issues is the place to discuss about phonopy issues.
- Github pull request is the place to request merging source code.

### Formatting

Formatting rules are found in `pyproject.toml`.

### pre-commit

Pre-commit (https://pre-commit.com/) is mainly used for applying the formatting
rules automatically. Therefore, it is strongly encouraged to use it at or before
git-commit. Pre-commit is set-up and used in the following way:

- Installed by `pip install pre-commit`, `conda install pre_commit` or see
  https://pre-commit.com/#install.
- pre-commit hook is installed by `pre-commit install`.
- pre-commit hook is run by `pre-commit run --all-files`.

Unless running pre-commit, pre-commit.ci may push the fix at PR by github
action. In this case, the fix should be merged by the contributor's repository.

### VSCode setting
- Not strictly, but VSCode's `settings.json` may be written like below

  ```json
  "ruff.lint.args": [
      "--config=${workspaceFolder}/pyproject.toml",
  ],
  "[python]": {
      "editor.defaultFormatter": "charliermarsh.ruff",
      "editor.codeActionsOnSave": {
          "source.organizeImports": "explicit"
      }
  },
  ```

## Documentation

Phonopy user documentation is written using python sphinx. The source files are
stored in `doc` directory. Please see how to write the documentation at
`doc/README.md`.

## How to run tests

Tests are written using pytest. To run tests, pytest has to be installed. The
tests can be run by

```bash
% pytest
```
oxaigen 0.0.3.4
Oxaigen Python SDK
Requires Python: <3.13,>=3.10.12

<div id="top"></div>
<!-- PROJECT LOGO -->
<br />
<div align="center">
<h1 align="center">Oxaigen Python SDK</h1>
  <p align="center">
    "Oxaigen Python SDK"
    <br />
  </p>
</div>

---

See the Oxaigen Knowledge base for the package documentation
navfitx 0.0.3a5
it's like NAVFIT98 but better
Requires Python: >=3.13

# NAVFITX

![PyPI - Version](https://img.shields.io/pypi/v/navfitx)

NAVFITX is a drop-in replacement for NAVFIT98A.

It's faster, less buggy, cross-platform, and provides more validation to reduce the number of rejected reports.

| Feature | NAVFIT98 v33 | NAVFITX | 
|---------|---------------|---------|
| Export Reports as PDF | ✅ | ✅ |
| Runs on Windows | ✅ | ✅ |
| Easy to install | ❌ | ✅ |
| Runs on MacOS | ❌ | ✅ |
| Runs on Linux | ❌ | ✅ |
| Install & Use w/out Admin Privileges | ❌ | ✅ |
| Export reports in a sqlite database | ❌ | ✅ |
| Export reports as JSON files | ❌ | ✅ |
| Export reports as [TOML](https://toml.io/) files | ❌ | ✅ |
| Export use via CLI | ❌ | ✅ |

## Installation

1. [Install uv](https://docs.astral.sh/uv/getting-started/installation/)
2. Run `uv tool install navfitx`.

## Usage

### Launch the GUI

`uvx navfitx`

### Use the CLI

`uvx navfitx --help`

## Help NAVFITX Succeed

### Feedback/Suggestions
If you find a bug, have a question, or have feedback/a request for an enhancement, please create a [new issue](https://github.com/tristan-white/navfitx/issues) to track it.

I'd like to see NAVFITX replace NAFIT98A in the fleet. I'm looking for user testimonials from anyone that's used NAVFIT98A or eNavFit in order to answer the "why is this important" when I make the pitch to current NAVFIT98 stakeholders within the Navy. If you have feedback on these programs, please provide it here:

- [Provide feedback on NAVFIT98A](https://github.com/tristan-white/navfitx/discussions/1)
- [Provide feedback on eNavFit](https://github.com/tristan-white/navfitx/discussions/2) (if you had the chance to use it before it was shut down)

### Star NAVFITX in Github

You can "star" [NAVFITX in GitHub](https://github.com/tristan-white/navfitx) (clicking the star button at the top right).

By adding a star, other users will be able to find it more easily and see that it has already been useful for others.
loreley 0.7.5a0
Whole-repository Quality-Diversity optimization for real git codebases.
Requires Python: >=3.11

## Loreley

> Whole-repository Quality‑Diversity optimization for real git codebases.

Loreley is a distributed system that **evolves entire git repositories** (the unit of search is a git commit). It continuously samples base commits, asks external planning/coding agents to implement repo-wide changes, evaluates the result with your evaluator, and stores metrics plus a MAP‑Elites archive in Postgres for later sampling and reuse.

![](./docs/assets/loreley.svg)

### Why use it

- **Whole-repo evolution**: cross-module refactors and “production-style” changes are first-class.
- **QD-native (MAP-Elites)**: keeps multiple high-performing but *different* solutions instead of a single champion line.
- **Learned behaviour space**: behaviour descriptors come from repo-state code embeddings (cached by git blob SHA), not hand-crafted heuristics.
- **Production loop**: scheduler + Redis/Dramatiq workers + Postgres, with preflight checks, logs, and reproducible git history.

### Quick start (local)

**Requirements**: Python 3.11+, [`uv`](https://github.com/astral-sh/uv), Git (worktrees), PostgreSQL, Redis, and an OpenAI-compatible API for embeddings (`OPENAI_API_KEY`). You also need:

- **Planning/coding backend**: default is the `codex` CLI on `PATH` (override via `WORKER_PLANNING_BACKEND` / `WORKER_CODING_BACKEND`).
- **Evaluator plugin**: `WORKER_EVALUATOR_PLUGIN=module:callable` that runs unattended and returns structured metrics.

```bash
git clone <YOUR_FORK_OR_ORIGIN_URL> loreley
cd loreley
uv sync
docker compose up -d postgres redis

cp env.example .env
# Minimal required vars:
# - OPENAI_API_KEY
# - MAPELITES_EXPERIMENT_ROOT_COMMIT=<git commit hash>
# - SCHEDULER_REPO_ROOT=/abs/path/to/your/target-git-checkout
# - WORKER_REPO_REMOTE_URL=<git remote URL with push access>
# - WORKER_EVOLUTION_GLOBAL_GOAL="..."
# - WORKER_EVALUATOR_PLUGIN=module:callable
# - (optional) WORKER_EVALUATOR_PYTHON_PATHS=["/abs/path/to/plugin_dir"]
# - (optional) SCHEDULER_STARTUP_APPROVE=true  # skip interactive startup approval

uv run loreley doctor --role all
uv run loreley scheduler
uv run loreley worker
```

### Optional UI (read-only)

```bash
uv sync --extra ui
uv run loreley ui
```

![](./docs/assets/ui.jpeg)

### Documentation

- [`docs/index.md`](docs/index.md) (local)
- [Online docs](https://NeapolitanIcecream.github.io/loreley/)
- Key guides: [`docs/loreley/config.md`](docs/loreley/config.md), [`docs/script/run_scheduler.md`](docs/script/run_scheduler.md), [`docs/script/run_worker.md`](docs/script/run_worker.md)
thunkmetrc 0.3.1
High-level ThunkMetrc Python SDK
Requires Python: >=3.10

# ThunkMetrc

High-level Python SDK for Metrc with convenience functions like `active_packages_inventory_sync`.

## Installation

```bash
pip install thunkmetrc
```

## Usage

```python
from thunkmetrc import active_packages_inventory_sync
from thunkmetrc_wrapper import MetrcWrapper

wrapper = MetrcWrapper("https://api.metrc.com", "vendor_key", "user_key")

# Sync active packages inventory
packages = active_packages_inventory_sync(
    wrapper,
    "license_number",
    last_known_sync=None,
    buffer_minutes=5
)
```

## License

MIT
thunkmetrc-wrapper 0.3.1
Type-safe wrapper for ThunkMetrc Python client
Requires Python: >=3.10

# ThunkMetrc Python Wrapper

Type-safe, rate-limited, async wrapper for the Metrc API.

## 📦 Installation

```bash
pip install thunkmetrc-wrapper
pip install thunkmetrc-client
```

## 🚀 Getting Started

### 1. Initialize
Use `MetrcFactory` to handle shared rate limiting effectively.

```python
import asyncio
from thunkmetrc.wrapper import MetrcFactory

async def main():
    # 1. Create Factory
    # Shared RateLimiter (150 requests/sec integrator limit)
    factory = MetrcFactory(max_concurrent_requests=150)

    # 2. Create Wrapper for specific license
    metrc = factory.create(
        base_url="https://sandbox-api-or.metrc.com",
        vendor_key="vendor_key",
        user_key="user_key"
    )
    
    # ...
```

### 2. Make Requests
All service methods are `async`.

```python
    try:
        facilities = await metrc.facilities.get_facilities()
        for f in facilities:
            print(f"Facility: {f.License.Number}")
    except Exception as e:
        print(f"Error: {e}")
```

### 3. Pagination (Async Iterator)
Use the `iterate_` methods to stream pages comfortably.

```python
    async for pkg in metrc.packages.iterate_get_active_packages(
        license_number="123-ABC-LICENSE"
    ):
        print(f"Package: {pkg.Label}")

if __name__ == "__main__":
    asyncio.run(main())
```

## 🛡️ Rate Limiting
The SDK uses `MetrcRateLimiter` to enforce:
- **Integrator Limits**: Default 150/sec.
- **Facility Limits**: Default 50/sec per facility.
- **Backoff**: Exponential backoff on 429/500 errors.
- **Retries**: Automatic retry logic.

Configuration is handled via `MetrcFactory`.