When comparing CherryPy vs web.py, the Slant community recommends CherryPy for most people. In the question“What are the best general-purpose Python web frameworks usable in production sites?” CherryPy is ranked 9th while web.py is ranked 13th. The most important reason people chose CherryPy is:
It's very easy to choose what processes you want by turning them on or off. You can also configure per-URL as well.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Robust configuration mechanism
It's very easy to choose what processes you want by turning them on or off. You can also configure per-URL as well.
Pro Has production-ready server
Comes with a production level wsgi server that can be used instead of / in addition to gunicorn etc.
Pro Helps you organize the structure of your code
CherryPy provides some dispatcher patterns that support a wide range of functionality and provide some helpful ways of organizing the code.
Pro Easy to set up and work with
Web.py is pretty easy to set up and start working with.
Cons
Con Lacking good documentation
CherryPy's documentation could use some work. It generally feels very slim and is seriously lacking in some parts. For a beginner who is just starting with Python Frameworks, working with CherryPy's documentation would be very hard.
Con Can feel constraining to work with
web.py does not have an ORM like Django, and it misses a lot of other features that it's competitors have. This can make developers feel too much constrained by this framework.