-
-
Notifications
You must be signed in to change notification settings - Fork 16.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flask app installed as egg raises builtins.NotADirectoryError for templates #1562
Comments
@davidmegginson, just stumbled across this myself. You can work around it by giving |
Thanks, Denis! That should make life much easier. I'll test when I'm back at my computer, then close. |
zip file; otherwise, it can't read its templates. See pallets/flask#1562
Confirmed. |
isnt the actual problem that a filesystemloader is used instead of a packageloader? |
@RonnyPfannschmidt - would that be a configuration error in my app, or a core problem with flask? I'm still relatively new to the world of Python and WSGI. |
problem with flask |
@RonnyPfannschmidt - would you want to create a new issue, referencing this one? This one has gone a bit off track, and I don't have the background to describe the problem properly. |
Prevents NotADirectoryError's in flask templates Ref.: pallets/flask#1562 pallets/flask#1645
Prevents NotADirectoryError's in flask templates Ref.: pallets/flask#1562 pallets/flask#1645
I've created a MANIFEST.in file and added the include_package_data flag to setup as recommended in #84 and have confirmed that the template files do appear in the egg file installed into my virtualenv:
When I run from the source directory, all is fine. When I try to run from the egg installed in the virtualenv, I get the following error:
The text was updated successfully, but these errors were encountered: