semvec/pypi-packages huggingface dataset:
miney 0.5.8
The python interface to Luanti
Requires Python: >=3.6

<p align="center">
<img src="https://github.com/miney-py/miney/raw/master/docs/miney-logo.png">
</p>

# Miney - The python interface to Luanti

Miney is the Python API to Luanti/Minetest.

Miney connects locally, over network or internet with the Luanti protocol and provides a pythonic interface to the server, players, blocks and more.

* `PyPI <https://pypi.org/project/miney/>`_

* `Luanti ContentDB <https://content.luanti.org/packages/Miney/miney/>`_

## Documentation

https://miney.readthedocs.io/en/latest/

## Status

https://miney.readthedocs.io/en/latest/changelog.html

**With version 0.5 we removed mineysocket and talking now directly to the server over the Luanti protocol.**

Miney is still in beta, so expect breaking changes.

## Requirement

* Python 3.6+ (tested on 3.12)
* Installed "miney" mod in the server.

# Development

Clone the repo:
```
git clone https://github.com/miney-py/miney.git
```

# TODO

A list of things i'm planning to do. There will be no fixed timeline. 

Feel free to contribute!

* [ ] Github-Actions
  * [ ] run tests
  * [ ] Tests for pull requests
  * [ ] Build and push to pypi for tagged commits
  * [ ] Build and push to Luanti ContentDB for tagged commits
* [ ] Callbacks
  * [x] Basic API and some callbacks implemented
  * [ ] Implement more "register_on_..." functions
* [ ] Mesecons: Add a python script processor that executes python code. 
* Documentation:
    * [ ] Better first steps guide
    * [ ] Python learning lessons that build on each other
    * [ ] Education material for beginners, teachers and students
    * [ ] Multilanguage
* Native client
    * [ ] Get chunks, blocks and positions of surrounding entities like a normal client
        * Could be interesting for machine learning and bots to make them aware of their surroundings
    * [ ] Normal player movement without using lua
    * [ ] Player interactions like punching and interacting with blocks and entities
* [ ] Asyncio
* Python driven mobs?
libsms 0.2.9
Interacting with the Simulating Microbial Systems (SMS Atlantis) API
Requires Python: >=3.11

[![Documentation](https://img.shields.io/badge/documentation-online-blue.svg)](https://libsms.readthedocs.io/en/latest/)
[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/drive/1UOA_qy_jprxKjsVewNrefiyGw7z_981D?usp=sharing)
[![CI](https://img.shields.io/github/actions/workflow/status/AlexPatrie/libsms/ci.yml?branch=main)](https://github.com/AlexPatrie/libsms/actions/workflows/ci.yml?query=branch%3Amain)

### Regarding SMS API:

The SMS(Simulating Microbial Systems) API allows users to design, run, and analyze reproducible simulations of dynamic cellular processes in Escherichia coli.
This tool aims to allow users to configure, run, and introspect simulations of the vEcoli(Vivarium-Ecoli) model. The SMS API uniquely acts as both a server
and client, using FastAPI, Uvicorn, and Marimo to serve a REST API as well as host Marimo user interfaces. The full comprehensive REST API documentation is
available at https://sms.cam.uchc.edu/redoc. Please refer to the aforementioned documentation for the complete details of the request query parameters and
body data required for each outlined endpoint.

Server-side sits kubernetes cluster containing a containerized ASGI(Asynchronous Server Gateway Interface) application using Python and FastAPI which is hosted and
available at https://sms.cam.uchc.edu/. An API router of endpoints is assigned for each API in this project's scope and available by name in the request url. The
primary modes of interaction exist within the "/wcm" and "/core" endpoint routers. For example, the primary single-cell API ("core") endpoints are hosted at https://sms.cam.uchc.edu/core.
A more generalized, Nextflow-based group of endpoints that is actively being developed is available at https://sms.cam.uchc.edu/wcm. Internally it uses a simulation service
that dynamically creates and dispatches SLURM job scripts which are executed through an authenticated connection with a given HPC(High Performance Computing) environment.

The /wcm endpoint router enables the design, execution, and introspection of simulations using vEcoli's Nextflow API. This is the preferred mode of interaction with
the SMS API, as it enables users to customize simulation configurations, create variants, run analysis, and execute a "batch" of one or many ecoli simulation jobs.
A typical end-to-end SMS API /wcm workflow consists of the following:

This project’s “client” behavior is leveraged by the utilization of Marimo(python) components rather than a traditional javascript-based frontend framework. A
static HTML Jinja template is served as an extension of the FastAPI/Uvicorn backend server enabling interactive simulation introspection. There exists a user
interface for each router within the set of routers exposed by the REST API. The user interface makes calls to the REST API to enable non-programmatic interaction
with the aforementioned endpoints. This UI is accessible by navigating to https://sms.cam.uchc.edu/.
repoconf 0.0.0.dev0
Centrally configure your decentralised git repo
Requires Python: >=3.12
Keywords: config, version-control, configuration, git, vcs, library, version control, centralized, central

# py-repoconf

![PyPI - Python Version](https://img.shields.io/pypi/pyversions/repoconf)
![PyPI - Types](https://img.shields.io/pypi/types/repoconf)
![GitHub License](https://img.shields.io/github/license/Vaastav-Technologies/py-repoconf)
[![🔧 test](https://github.com/Vaastav-Technologies/py-repoconf/actions/workflows/test.yml/badge.svg)](https://github.com/Vaastav-Technologies/py-repoconf/actions/workflows/test.yml)
[![💡 typecheck](https://github.com/Vaastav-Technologies/py-repoconf/actions/workflows/typecheck.yml/badge.svg)](https://github.com/Vaastav-Technologies/py-repoconf/actions/workflows/typecheck.yml)
[![🛠️ lint](https://github.com/Vaastav-Technologies/py-repoconf/actions/workflows/lint.yml/badge.svg)](https://github.com/Vaastav-Technologies/py-repoconf/actions/workflows/lint.yml)
[![📊 coverage](https://codecov.io/gh/Vaastav-Technologies/py-repoconf/branch/main/graph/badge.svg)](https://codecov.io/gh/Vaastav-Technologies/py-repoconf)
[![📤 Upload Python Package](https://github.com/Vaastav-Technologies/py-repoconf/actions/workflows/python-publish.yml/badge.svg)](https://github.com/Vaastav-Technologies/py-repoconf/actions/workflows/python-publish.yml)
![PyPI - Version](https://img.shields.io/pypi/v/repoconf)

---

**🧠 Centrally configure your decentralised 🐙 git repo.**

Git, being an awesomely decentralised system, has ways to have decentralised configurations per user. However, 
times require certain configurations to be shared and tracked centrally among various collaborators. Some examples of
centrally sharable configurations are:

- 💻 Branch descriptions (or better, branch READMEs).
- 💡Issues/Features/Tasks related to the repo.
- 🪼 Certain properties that closely relate to the repo.
- 📕 Rules related to per-branch collaborations and conventions.
- 🔒 Encrypted secrets.
- 🎁 Deployment, packaging and distribution mechanics.
- ⬆️ ... and more


Repoconf is developed to address this issue. It stores central configuration in the `__repoconf/default/main` branch
and this centrally stored distributed configuration can be:

- 🟢 accessed using git config commands and aliases
- ➕ added
- ➖ removed
- ↗️ pushed
- ↙️ pulled

... just like any other git branches 👏👻.

## Quick Start

### Command usage

* List all the configurations for the current repo

    ```shell
    repoconf config --list
    ```

* Add configuration

    ```shell
    repoconf config branch.my-branch.description "This branch is created for something which one may not readily remember in the future."
    repoconf config branch.my-sharable-branch.description "This branch is to be shared with others and thus requires concise description on what it is created for."
    ```

... supports nearly all options that `git config` command supports. 
See [git config documentation](https://git-scm.com/docs/git-config) for more details.

## Installation

```shell
pip install repoconf
```