semvec/pypi-packages huggingface dataset:
gist-protocol 0.0.1
Semantic transport protocol for bandwidth-constrained channels
Requires Python: >=3.9
Keywords: gist, protocol, semantic, transport, codebook, compression

# gist-protocol

Semantic transport protocol for bandwidth-constrained channels.

GIST transmits compact codebook coordinates instead of high-dimensional feature vectors — enabling real-time semantic communication over constrained links like BLE, LoRa, and satellite.

## Status

**Coming soon.** This package is a name reservation. The full implementation is in active development.

## What to expect

- Codebook-based encode/decode for semantic features
- Session management with HMAC authentication
- Support for audio, ECG, IMU, and text domains
- Embedded C library for microcontrollers (Cortex-M4+)
- Sub-millisecond encode latency, 2-byte wire payloads

## Install

```bash
pip install gist-protocol
```

## CLI

```bash
gist            # prints project info
gist --version  # prints version
```
audiogen 0.2.0
Generator based tools for working with audio clips.

Audiogen
========

The ``audiogen`` package provides time domain audio processing tools
using Python generators.

This makes some types of audio sample generation and processing pretty
easy::

	# mix 440 Hz and 445 Hz tones to get 5 Hz beating
	beats = audiogen.util.mixer(
		(audiogen.tone(440), audiogen.tone(445)),
		[(constant(1), constant(1)),]
	)

The actual samples won't be generated or stored in memory until they're
actually consumed – for instance, when they're being written out to disk
in a wave \file::

    with open("output.wav", "wb") as f:
        audiogen.sampler.write_wav(f, beats)

Generators' at-consumption-time computation also allows creating
infinitely long output, e.g. to stream to speakers rather than a file on
disk::

    audiogen.sampler.write_wav(sys.stdout, audiogen.tone(440))

Or just::

    audiogen.sampler.play(audiogen.tone(440))

You can also use standard generator tools, e.g. the itertools module, to
handle audio data::

	beep_silence = itertools.chain(audiogen.beep(), audiogen.silence(0.5))
	infinite_beeps = itertools.cycle(beep_silence)

    audiogen.sampler.write_wav(sys.stdout, infinite_beeps)

Soundcard output
----------------

The easiest way to play directly to a soundcard output is to use the
``audiogen.sampler.play`` function, which will play your samples using
PyAudio::

    import audiogen
    import itertools
    import sys

    audiogen.sampler.play(
        itertools.cycle(itertools.chain(audiogen.beep(), audiogen.silence(0.5)))
    )

Alternatively, you could write your wave data to ``stdout``, e.g. ``myaudio.py``::

    import audiogen
    import itertools
    import sys

    audiogen.sampler.write_wav(
        sys.stdout,
        itertools.cycle(itertools.chain(audiogen.beep(), audiogen.silence(0.5)))
    )

Then pipe to a command line audio player like Sox_::

    python myaudio.py | play -t wav -

Installation
------------

Install with::

    $ pip install audiogen
    $ pip install --allow-external PyAudio --allow-unverified PyAudio PyAudio

PyAudio is optional. If it's not installed, playing audio via the soundcard with
``audiogen.sampler.play()`` will not be available, but generating Wave files –
including for piping to an external player, like ``sox`` – will work just fine.

Note that to install PyAudio on Mac OS X, you'll need to first install `portaudio`::

    $ brew install portaudio

See also
--------

Projects built with ``audiogen``:

- `koch <https://github.com/casebeer/koch>`__, a Koch method Morse code trainer and audio generator
- `afsk <https://github.com/casebeer/afsk>`__, a ham radio APRS/Bell-202 audio frequency shift keying encoder

Contributing
------------

Get the source and report any bugs on Github:

    https://github.com/casebeer/audiogen

Version history
---------------

- 0.1.2 - Add band pass and band stop IIR filters; custom beep lengths from @jhobbs
- 0.1.1 - Fix multiplexing bug causing increase in pitch when using mixer() to produce
  more than one output channel
- 0.1.0 - Breaking changes: new arguments to tone(), play() blocks by default

.. _Sox: http://sox.sourceforge.net/
datui 0.2.49
Data Exploration in the Terminal
Requires Python: >=3.10
Keywords: datui, data, polars, tui, dataframe, eda, tables

# Datui

Explore Polars DataFrames in the terminal.

To learn more, see the [full documentation](https://derekwisong.github.io/datui/).

## Installation

Install Datui with `pip`:

```
pip install datui
```

## Usage

**View a LazyFrame or DataFrame**

```python
import polars as pl
import datui

# From a LazyFrame (e.g. scan)
lf = pl.scan_csv("data.csv")
datui.view(lf)
```

Press `q` to exit Datui and return to Python.

## Run at the Command Line

Run the `datui` command line application:

```bash
datui /path/to/data.parquet
```

For help:

```bash
datui --help
```
kraken-engine 1.6.1
Python bindings for Kraken Engine
Requires Python: >=3.11

<div align="center"><img src="https://github.com/durkisneer1/Kraken-Engine/blob/main/docs/_static/kraken-engine-banner.png"/></div>

<div align="center">
  <img src="https://img.shields.io/badge/license-MIT-blue.svg">
</div>

<br>

**Kraken Engine** is a modern, lightweight 2D game development Python library with the speed of C++, designed to give developers the power and flexibility of low-level systems with the ease of a clean, expressive API.
It is ideal for solo developers and indie teams looking to build games or interactive experiences rapidly.

## Documentation

You can find the latest documentation at [https://docs.krakenengine.org/](https://docs.krakenengine.org/).

## Community

A community Discord server is available at [https://discord.gg/jMdx9UmqX8](https://discord.gg/jMdx9UmqX8).

Join to get help or share your Kraken Engine games!

## Licensing

[MIT](LICENSE) @ Derrick Martinez

`Kraken Engine` is a free and open-source framework built for education and fast prototyping.
astropy-iers-data 0.2026.2.16.0.48.25
IERS Earth Rotation and Leap Second tables for the astropy core package
Requires Python: >=3.8
Keywords: IERS, astropy, data

IERS Earth Rotation and Leap Second tables for the astropy core package
-----------------------------------------------------------------------

.. image:: https://zenodo.org/badge/644894042.svg
   :target: https://zenodo.org/badge/latestdoi/644894042

**Note:** This package is not currently meant to be used directly by users, and only
meant to be used from the core astropy package.

https://docs.astropy.org/en/latest/utils/iers.html

License
-------

This project is Copyright (c) Astropy Developers and licensed under
the terms of the BSD 3-Clause license. This package is based upon
the `OpenAstronomy packaging guide <https://github.com/OpenAstronomy/packaging-guide>`_
which is licensed under the BSD 3-clause licence. See the licenses folder for
more information.


Contributing
------------

We love contributions! astropy-iers-data is open source,
built on open source, and we'd love to have you hang out in our community.

**Imposter syndrome disclaimer**: We want your help. No, really.

There may be a little voice inside your head that is telling you that you're not
ready to be an open source contributor; that your skills aren't nearly good
enough to contribute. What could you possibly offer a project like this one?

We assure you - the little voice in your head is wrong. If you can write code at
all, you can contribute code to open source. Contributing to open source
projects is a fantastic way to advance one's coding skills. Writing perfect code
isn't the measure of a good developer (that would disqualify all of us!); it's
trying to create something, making mistakes, and learning from those
mistakes. That's how we all improve, and we are happy to help others learn.

Being an open source contributor doesn't just mean writing code, either. You can
help out by writing documentation, tests, or even giving feedback about the
project (and yes - that includes giving feedback about the contribution
process). Some of these contributions may be the most valuable to the project as
a whole, because you're coming to the project with fresh eyes, so you can see
the errors and assumptions that seasoned contributors have glossed over.

Note: This disclaimer was originally written by
`Adrienne Lowe <https://github.com/adriennefriend>`_ for a
`PyCon talk <https://www.youtube.com/watch?v=6Uj746j9Heo>`_, and was adapted by
astropy-iers-data based on its use in the README file for the
`MetPy project <https://github.com/Unidata/MetPy>`_.