An example would be that Bottle creates an application object implicitly and assumes that all resources(templates, static files, etc.) are relative to the cwd. However the WSGI specification doesn't define what the cwd points to so you have to work around that for some servers.
If you use Flask you create the application object explicitly and pass it the name of the module, relative to which Flask looks up resources.
In the big picture, I don't see having to write a wrapper function for template rendering with a fixed template_lookup argument being a big deal (I'm basing all of my judgments on source alone, I've only fiddled with either framework).
Comments
An example would be that Bottle creates an application object implicitly and assumes that all resources(templates, static files, etc.) are relative to the cwd. However the WSGI specification doesn't define what the cwd points to so you have to work around that for some servers.
If you use Flask you create the application object explicitly and pass it the name of the module, relative to which Flask looks up resources.
> assumes that all resources(templates, static files, etc.)
Reading the source, I see no evidence of this.
https://github.com/defnull/bottle/blob/master/bottle.py#L161...
I must have been mistaken for static files, for templates however it is the case:
https://github.com/defnull/bottle/blob/master/bottle.py#L263...
You can override it but you would have to do that for every call to `template` or by monkey patching `TEMPLATE_PATH`.
In the big picture, I don't see having to write a wrapper function for template rendering with a fixed template_lookup argument being a big deal (I'm basing all of my judgments on source alone, I've only fiddled with either framework).
It's still a problem for modularity, something like Flask's blueprints are basically impossible for Bottle.