esper VS snecs

That's cool, I didn't realize you had implemented an ECS library for tcod. At first glance it seems a bit more featureful than esper. The tags and relations functionality seem particularly useful for queries. l'll consider using it for the tutorial.

If you don't mind the broken type hinting then you could go with Esper.

I've been closely looking at the Python ECS libraries Snecs and Esper. I was hoping I could use one of them to fix the Python tutorial without making the tutorial about writing an entity-component engine. What I actually want would be a Python ECS library with NumPy for static types, but a library I did find for that didn't have a good enough license for a tutorial. For now I'll be okay with dynamic types just so I can fix my current problems, and I'll think about performance some other time.

I've been attempting to do this using an entity-component-system (specifically the Esper system). The difference being that I'm trying to explain my processors in separate documents first.

Not much to see/to do yet. I just wanted to try Esper and LDtk.

I tried to use Snecs but its type-hinting was not robust enough for VSCode's Pylance. I had to throw it out and make my own simplified version of ECS. I can add single arbitrary components to entity objects but I don't have a global registry for them. Which is too bad since the global registry is a useful and important part of ECS.

I've been closely looking at the Python ECS libraries Snecs and Esper. I was hoping I could use one of them to fix the Python tutorial without making the tutorial about writing an entity-component engine. What I actually want would be a Python ECS library with NumPy for static types, but a library I did find for that didn't have a good enough license for a tutorial. For now I'll be okay with dynamic types just so I can fix my current problems, and I'll think about performance some other time.