Is there a reason you didn't use SQLAlchemy, as that's what I turn to when I'm not in Django-land. It's also closer to a competitor to Peewee than Django's ORM

Is there a reason you didn't use SQLAlchemy, as that's what I turn to when I'm not in Django-land. It's also closer to a competitor to Peewee than Django's ORM is. I mean, when I use Django, even though I could switch out the ORM, I'd be ditching a lot of freebies (integration with auth, forms, South, all the reusable apps in the wild). Thus, you really don't see people ripping out the Django ORM except in the very extreme cases. It also explains why it'll be really difficult to switch out the Django ORM, as there is just so much integration to rewrite and legacy apps to lose. If I wanted/needed/was willing to reinvent all of that, I'd probably start with a smaller framework (like Tornado, Flask) where the only stable game - so far - is SQLAlchemy. Thus, I don't think it's in your benefit to consider/advertise yourself a lightweight alternative to the Django ORM, as there aren't many folks looking for an alternative (and even though most people aren't 100% happy with Django's ORM the bar to competing is really high). Your users are most likely not using Django, and deciding between Peewee and SQLAlchemy.