Livecoding Mode for Python

Aperta
#61 4 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@catilac ci sta già lavorando.

Dal 24/1/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Leverage bevy_ecs to watch the currently running sketch for changes and hotswap on successfully compiling edits

Edit: I'm currently working on this, but there are some architectural questions I have.

Current Approach

I've created a new bevy Asset called Sketch and spawn that object at Startup.
When I make a change to sketch.py bevy will notice. yay

The question now is how does the actual reloading mechanism work for Python? And there is a larger question of how does this mechanism work for other language frontends (Processing4/java, lua, ocaml, scheme, ruby, etc...)

For Python (w/ pyo3)

  1. Make a change to sketch.py
  2. Bevy will observe and [emit an event]
  3. processing_pyo3 crate will check if a reload is necessary
  4. Using something like importlib.reload(), pyo3 can reload the module, and skip creating a new graphics context if it doesn't have to, and grab the new draw and setup functions.
+--------+        +------+
| Python |------->| Bevy |
+--------+        +------+
   ^                |
   |                |
   +-- onChange ----+

What about other language front-ends?

I suppose some custom plugin loading could work. The Sketch Asset could be something that Python introduces, so that would allow for us to only use any of that design only for our pyo3 implementation

The other front-ends would have to build their own systems, and we could expose hot-reloading related FFI methods?

I think at the moment, I really like the idea of just having a Python related Livecoding bevy plugin. I'm still learning about bevy's ECS system, but is it possible for us to represent our "scene graph" as an intermediary that can easily map to the existing entities in bevy?

ie:

def draw():
    background(220)

    fill(255, 0, 100)
    stroke(0)
    stroke_weight(2)
    rect(100, 100, 200, 150)

when I change stroke_weight, could bevy know to update, or refresh that particular entity?
or is it easier to just drop all the entities and re-run the sketch? I might be over thinking it.

For now I'm going to work towards getting python to hotreload.

Lingua principale
Rust
Stelle
69
Fork
14
Merge medio
15g 22h
PR unite (30g)
3

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di processing/libprocessing

Tutte le issue di processing/libprocessing

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.