You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems to be related to the fact that I explicitly set the TEMPLATE_PATH to ensure the template files are found when using a package structure (my template is in my_package/views/testing.jinja2):
The above code is referenced from the my_package/__main__.py file. Running python -m my_package from the parent directory of the package yields the above warning.
Without adding the new template path, browsing to the page yields error code 500 with
Template 'testing.jinja2' not found.
What is the correct way to resolve the templates when using a "real" package structure?
The text was updated successfully, but these errors were encountered:
Oh, that makes sense. So jinja2 is turing it into an absolute path name and then bottle is complaining.
So we don't know why the author decided to depreciate this in 0.12, but that was probably a mistake. Note that the code just complains and then goes ahead and returns an absolute path!!! So I think that this is a bug in bottle.
I am currently getting the following warning:
This seems to be related to the fact that I explicitly set the
TEMPLATE_PATH
to ensure the template files are found when using a package structure (my template is inmy_package/views/testing.jinja2
):The above code is referenced from the
my_package/__main__.py
file. Runningpython -m my_package
from the parent directory of the package yields the above warning.Without adding the new template path, browsing to the page yields error code 500 with
What is the correct way to resolve the templates when using a "real" package structure?
The text was updated successfully, but these errors were encountered: