peewee

I have not used Peewee, but at first sight the most visible difference is the query syntax - Peewee uses method chaining, whereas Pony ORM decompiles Python AST.

Suspicious that aiohttp has peewee async, but falcon gets synchronous sqlalchemy for its orm test?

When I use Peewee ORM with Python, I use Postgres in production and SQLite in-memory for testing.

To be honest I'm somewhat second guessing my decision, because Peewee is far from the Python standard.

On there other side, it seems Peewee already has migration support, whereas in Pony migrations are not implemented yet, this is the next task.

I'm not sure that Kip and Peewee would have survived 5+ days at 8 g.

Toss in Peewee as well (another single file) and I get a decent ORM.

I haven't used it myself, but I took a good look at the code for PeeWee for some changes I wanted to make to Django.

I like to pair this with Peewee (included in the webpy-skeleton).

I'm the author of a lightweight python ORM (peewee) and have a healthy respect for the work that goes into building this type of tool.

I use PeeWee but prefer to use just raw SQlite.

When Python ORM is required, I'm using peewee.

I'm mostly familiar with the Flask+Peewee stack when writing web apps, but migrating shouldn't be an issue (even if it's another language).

I've enjoyed using Peewee[1] as a lightweight ORM for Python - mainly for scripting data manipulation on legacy databases but it does the job nicely.

Django: Item.objects.filter(price__gt=3) Pony ORM: select(o for o in Item if o.price>3) Peewee: Item.select().where(Item.price>3) Kohana: $Item->where('price', '>', 3)->find(); You see, the __gt or '>' here is kind of stupid.