semvec/pypi-packages huggingface dataset:
komida 0.0.4
Komida API.
Requires Python: >=3.10
Keywords: komida, api

# Komida API (komida)

Returns structured data from the [komida calendar][calendar].

## Getting Started

Start by installing the dependencies using pip.
One way of doing this is `pip install -r requirements.txt`.
This will install **all** dependencies, including those used for development.
To only install the minimum set of requirements and the package use `pip install -e .`.

You can also install the latest release with `pip install kapi`.

## Example

```python
from datetime import datetime
from komida import KomidaAPI, Request, Location, Customer

api = KomidaAPI()
my_request = Request(Location.MIDDELHEIM, Customer.ANTWERPEN, datetime(2024, 10, 1))
menu = api.get_menu(my_request)
print(len(menu.dishes))
for dish in menu.dishes:
    for ingredient in dish.ingredients:
        print(ingredient)
print(menu.contains_dish("chicken"))
```

## Improvements

- Sanitize the data
- Fix allergens

[calendar]: https://app.growzer.be/komida-calendar
rl-cli 0.0.1
Runloop CLI for interacting with the Runloop APIs.

# rl-cli
A command line utility for interacting with runloop APIs.

**NOTE: This project is still in early alpha release**

# Setup

(Homebrew instructions coming soon...)

## For developers
```commandline
# Clone the repo
mkdir -p ~/source/ && cd ~/source/
git clone https://github.com/runloopai/rl-cli.git
cd rl-cli/

# Setup the venv and dev tools
python3 -m venv .venv && source .venv/bin/activate && pip install -r dev-requirements.txt

# Install to your local machine
# Use 'which python3' to find your system python
flit install --symlink --python </path/to/system/python>
```

```
# In a new terminal
export RUNLOOP_API_KEY=<your-api-key>
rl --help
```

# Quick reference

## Devbox

### Create a devbox and run a single command
```commandline
rl devbox create --env_vars HELLO=world --entrypoint 'echo $HELLO'
>
create devbox={
    "id": "dbx_2xMDUOsKMiZBYKsvSRtMA",
    "blueprint_id": null,
    "create_time_ms": 1723229557715,
    "end_time_ms": null,
    "initiator_id": null,
    "initiator_type": "invocation",
    "name": null,
    "status": "provisioning"
}
```

### Observe logs
```commandline
rl devbox logs --id dbx_2xMDUOsKMiZBYKsvSRtMA
>
2024-08-09 12:15:01.701  Initializing devbox...
2024-08-09 12:15:01.734  Devbox setup complete
2024-08-09 12:15:01.769 [entrypoint] -> echo $HELLO
2024-08-09 12:15:01.798 [entrypoint]  world
2024-08-09 12:15:01.798  world
2024-08-09 12:15:01.800 [entrypoint] -> exit_code=0
```

### Check the devbox status
```commandline
rl devbox get --id dbx_2ws7IOtjxnJgLsBIpU9nn
>   
# Note that the devbox status="shutdown" after the entrypoint completes.
devbox={
    "id": "dbx_2xMDUOsKMiZBYKsvSRtMA",
    "blueprint_id": null,
    "create_time_ms": 1723229557715,
    "end_time_ms": 1723229561620,
    "initiator_id": null,
    "initiator_type": "invocation",
    "name": null,
    "status": "shutdown"
}
```