[andybak]

The great thing about the Django Admin is that - because it was actually part of the Django itself - there is a whole ecosystem of extensions, add-ons, skins etc for it.

Any attempts to replace it for Django would have an uphill struggle for that reason alone.

This is one side-effect of an opinionated framework - the provision of a default choice facilitates cooperation and prevents fragmentation.

(We recently picked up a Pyramid project and I was rather surprised how big the impact was of the extra choice. Simply in terms of searching for answers to questions - we often had to find an answer from someone who was using the same combination of parts that we were using. And figuring out how to do x often fell into the gaps in the docs between two components and was therefore harder to figure out)

[theVirginian]

Possibly you also ran into the Q/A problem because there are many more people who use Django and common issues/gotchas that people encounter have mostly been explored and documented. I haven't used Pyramid but I would imagine the user base is somewhat smaller.

[odonnellryan]

I've used Django Admin, and it is definitely really cool. However, I don't think it comes close to being a requirement for web development.

The awesome thing about Flask is you really only need to use what you need to use.

Flask also has really great support/docs/etc. I haven't had to google much to find answers to even the more obscure (use xyz supporting library) questions.

Not to be a Flask fanboy... Django definitely has its place. Flask works well for me.

[Walkman]

The thing is with Pyramid IMO that you have to have some experience with Python (and its ecosystem) to be able to use it effectively. It's clealry much more flexible than either Django or Flask and has more advanced concepts and features (such as view predicates, declarative permission system, URL traverse, etc...) but you have to be able to use it.