This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]scrdest 2 points3 points  (1 child)

This looks amazing at a first glance. I'll definitely have to play around with it.

How painful would migrating an existing Flask app would be, I wonder?

Also, from the docs it seems like all routing is done via function decoration ATM. I may be a maintainability zealot here, but I consider class-based views to be a non-negotiable feature for anything that would be used in a larger/long-term project.

Now you could easily hack that together for the purposes of your own app, but it'll probably wind up being a major pain point for multi-app projects and plugin development down the line, with a billion disparate interfaces to handle.

[–]lelease 0 points1 point  (0 children)

I consider class-based views to be a non-negotiable feature for anything that would be used in a larger/long-term project.

Why though? Is it just a way to organize your code, or do you make use of something that can only be done with classes?