[purrpit]

>> POST to views loses POST data

>The middlewares shouldn't be redirecting POSTs then! They could have returned a client error instead.

It does raise RuntimeError during development

>> Integer & NULLS

>If the admin interface knows the field is required, why does it even attempt to insert a null value? It could return a validation error.

Maintaining integrity is databases' job primarily, also I could have triggers and functions inside my database to fallback to some default value when there isn't one incoming. This isn't an uncommon setup.

>> Appending to a list in session doesn't work

>Django's behavior with ORM relationships has always disappointed me. There's no way to work with them in memory like in SQLAlchemy because they always attempt to sync out changes to the database immediately. As a result you often have to write some very strange code. They could change this.

Where did ORM come from? Session backends are not exclusively written to be stored in databases.

>> Errors about undefined attributes with one-char names

>They could have done a type check to see if you passed a string instead of an iterable of strings.

...etc.

This way they'd have to type check at thousands of other places where types are assumed. If one isn't comfortable with python's syntactical sugar coatings - inevitably leading to some syntax gotchas, then they should move to more statically typed language.