semvec/pypi-packages huggingface dataset:
friend-lite-sdk 0.3.0
Python SDK for OMI/Neo1 BLE wearable devices — audio streaming, button events, and device control
Requires Python: >=3.10
Keywords: ble, bluetooth, wearable, omi, audio, streaming

# friend-lite-sdk

Python SDK for OMI / Friend Lite BLE wearable devices — audio streaming, button events, device control, and transcription.

Derived from the [OMI Python SDK](https://github.com/BasedHardware/omi/tree/main/sdks/python) (MIT license, Based Hardware Contributors). See `NOTICE` for attribution.

## Installation

```bash
pip install friend-lite-sdk
```

With optional transcription support:

```bash
pip install "friend-lite-sdk[deepgram]"   # Deepgram cloud transcription
pip install "friend-lite-sdk[wyoming]"    # Local ASR via Wyoming protocol
pip install "friend-lite-sdk[deepgram,wyoming]"  # Both
```

## Features

- **BLE Audio Streaming** — Connect to OMI/Friend Lite devices and stream Opus-encoded audio
- **Button Events** — Subscribe to single tap, double tap, long press events
- **Haptic Control** — Trigger haptic feedback patterns on supported devices
- **WiFi Sync** — Configure and trigger WiFi-based audio sync
- **Storage Access** — Read stored audio from device storage
- **Neo1 Support** — Sleep/wake control for Neo1 devices
- **Transcription** — Built-in Deepgram and Wyoming ASR integration

## Quick Start

```python
import asyncio
from friend_lite import OmiConnection, ButtonState, parse_button_event

async def main():
    async with OmiConnection("AA:BB:CC:DD:EE:FF") as conn:
        # Stream audio
        await conn.subscribe_audio(lambda _handle, data: print(len(data), "bytes"))

        # Listen for button events
        await conn.subscribe_button(
            lambda _handle, data: print("Button:", parse_button_event(data))
        )

        await conn.wait_until_disconnected()

asyncio.run(main())
```

## Device Discovery

```python
import asyncio
from friend_lite import print_devices

asyncio.run(print_devices())
```

## Links

- [Chronicle Project](https://github.com/SimpleOpenSoftware/chronicle)
- [Original OMI Project](https://github.com/BasedHardware/omi)
gracedb-sdk 1.0.0a1
REST API SDK for GraceDB
Requires Python: >=3.9

# gracedb-sdk

A modern, performant REST API client for GraceDB, based on [httpx](https://www.python-httpx.org). For documentation, see https://gracedb-sdk.readthedocs.io.

## Benchmarks

Time in seconds to perform common tasks [lscsoft/ligo-gracedb](https://git.ligo.org/lscsoft/gracedb-client). Measured on a residential Internet connection on the US East Coast.

![benchmarks compared to ligo-gracedb](https://git.ligo.org/emfollow/gracedb-sdk/snippets/92/raw)
hatch-pinned-extra 0.1.3
Add a packaging extra with pinned dependencies from a lock file
Requires Python: >=3.9

<div align="center">

<h1>hatch-pinned-extra</h1>

[![License][license-badge]][license]
[![GitHub last commit][commits-latest-badge]][commits-latest]
[![PyPI - Downloads][pypi-downloads-badge]][pypi-downloads]
[![uv][uv-badge]][uv]

Hatch plugin that adds a packaging [_extra_][extras] to the wheel metadata with pinned dependencies from [`uv.lock`][uvlock].

</div>

## Usage

```toml
# pyproject.toml
[build-system]
requires = [
    "hatchling",
    "hatch-pinned-extra>=0.0.1,<0.1.0",
]
build-backend = "hatchling.build"

[tool.hatch.metadata.hooks.pinned_extra]
name = "pinned"
```

If your package doesn't have any optional dependencies already, you will need to mark them as _dynamic_:

```toml
# pyproject.toml
[project]
dynamic = [
    "optional-dependencies",
]
```

### Enabling the Plugin

The plugin requires the `HATCH_PINNED_EXTRA_ENABLE` environment variable to be set to a truthy value to activate (e.g. `1`, `true`, `yes`, `on`). This design allows you to control when pinned dependencies are included:

```bash
# Build with pinned dependencies
HATCH_PINNED_EXTRA_ENABLE=1 uv build

# Update lockfile without constraints from pinned dependencies
uv lock --upgrade
```

This approach solves the circular dependency issue where pinned dependencies become constraints during `uv lock --upgrade`, preventing actual upgrades.

[license]: https://pypi.python.org/pypi/hatch-pinned-extra
[license-badge]: https://img.shields.io/pypi/l/hatch-pinned-extra.svg

[commits-latest-badge]: https://img.shields.io/github/last-commit/edgarrmondragon/hatch-pinned-extra
[commits-latest]: https://github.com/edgarrmondragon/hatch-pinned-extra/commit/main

[pypi-downloads-badge]: https://img.shields.io/pypi/dm/hatch-pinned-extra
[pypi-downloads]: https://pypi.python.org/pypi/hatch-pinned-extra

[uv-badge]: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/uv/main/assets/badge/v0.json
[uv]: https://github.com/astral-sh/uv

[extras]: https://packaging.python.org/en/latest/specifications/core-metadata/#provides-extra-multiple-use
[uvlock]: https://github.com/astral-sh/uv
SURE-tools 4.0.14
Succinct Representation of Single Cells
Requires Python: >=3.10

# SURE: SUccinct REpresentation of cells
 SURE implements a discrete latent state model with normalizing flow encoder for exact estimation of cellular populations. 


## Installation
1. Create a virtual environment
```bash
conda create -n SURE python=3.10 scipy numpy pandas scikit-learn && conda activate SURE
```

2. Install [PyTorch](https://pytorch.org/get-started/locally/) following the official instruction. 
```bash
pip3 install torch torchvision --index-url https://download.pytorch.org/whl/cu126
```

3. Install SURE
```bash
pip3 install SURE-tools
```
pkg-resources-backport 1.0.1
snapshot of last pkg_resources module from setuptools
Requires Python: >=3.9
Keywords: pkg-resources, pkgresources, setuptools

========================
pkg-resources backport
========================

For when your runtime dependencies absolutely require ``pkg-resources`` but you're unable to downgrade to setuptools 80.10.x.

.. code:: console

    (cpython312) autumn@JudgmentOfCarrion{arm64}:~/software# python -m pip install -U setuptools
    Requirement already satisfied: setuptools in /Users/autumn/.virtualenvs/cpython312/lib/python3.12/site-packages (80.9.0)
    ... /snip
    Successfully installed setuptools-82.0.0
    (cpython312) autumn@JudgmentOfCarrion{arm64}:~/software# python
    Python 3.12.12 (main, Oct  9 2025, 11:07:00) [Clang 17.0.0 (clang-1700.4.4.1)] on darwin
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import pkg_resources
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
    ModuleNotFoundError: No module named 'pkg_resources'
    >>> ^D
    (cpython312) autumn@JudgmentOfCarrion{arm64}:~/software# cd pkg-resources-backport
    (cpython312) autumn@JudgmentOfCarrion{arm64}:~/software/pkg-resources-backport# python -m pip install -e .
    Obtaining file:///Users/autumn/software/pkg-resources-backport
    ... /snip
    Successfully built pkg-resources-backport
    Installing collected packages: pkg-resources-backport
    Successfully installed pkg-resources-backport-1.0.0
    (cpython312) autumn@JudgmentOfCarrion{arm64}:~/software/pkg-resources-backport# cd ..
    (cpython312) autumn@JudgmentOfCarrion{arm64}:~/software# python
    Python 3.12.12 (main, Oct  9 2025, 11:07:00) [Clang 17.0.0 (clang-1700.4.4.1)] on darwin
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import pkg_resources
    >>> ^D
    (cpython312) autumn@JudgmentOfCarrion{arm64}:~/software#
xslope 0.1.19
Slope stability analysis (limit equilibrium and FEM) in Python.
Requires Python: >=3.9
Keywords: slope, stability, geotechnical, FEM, limit equilibrium

# xslope
Python package for limit equilibrium slope stability analysis

## License

This project is licensed under the Apache License, Version 2.0 - see the [LICENSE](LICENSE) file for details.

## Copyright

Copyright 2025 Norman L. Jones

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
omop-semantics 0.1.10
Add your description here
Requires Python: >=3.12

# omop_semantics

**omop_semantics** is a Python library for defining and managing **semantic conventions on top of OMOP CDM**.

It lets you describe conventions in code

- which OMOP concepts you want to have on hand as named key concepts to improve ergonomics in analytic code,
- how they are grouped,
- what roles they play 
- and provide profiles to render these targets uniformly into CDM tables.

The goal is to make these conventions **explicit, versioned, and reusable**, instead of being buried in code, SQL, or documentation. They are also extensible so that you can add opinionated layers on top of default specifications that may be relevant in a domain-specific context only.

---

## Key ideas

- **Human-authored**  
  Semantic rules and concept groups are written in YAML and validated with schemas.

- **Portable**  
  No database or graph store required.

- **Versionable**  
  Conventions can evolve over time and be tracked in git.

- **Integrates with pipelines**  
  Can drive ETL logic, validation, and documentation so they stay in sync.

---

## Typical workflow

1. **Define a schema**  
   Describes what kinds of semantic objects and roles exist (e.g. staging, modifiers).

2. **Write YAML instances**  
   Lists actual OMOP concepts and groups used in your project.

3. **Load a runtime registry**  
   This gives you a programmatic API to query concepts, groups, and relationships.

4. **Use it in code**  
   For validation, cohort logic, ETL constraints, or documentation.

---

## When should you use this?

Use **omop_semantics** if you:

- have project-specific rules about which OMOP concepts are valid,  
- need consistent concept groupings across ETL and analytics,  
- want semantic conventions to be explicit, testable, and versioned,  
- are working in domains like oncology where OMOP alone is too permissive.