The specific error you created, which was a syntax error, would cause the WSGI script file to even load into mod_wsgi. The error for this would end in the Apache error log file, and not in the log file that you configure using the log module. Have you looked at the Apache error log file?
For an exception that occurred during the execution of a request, Flask will turn it into a 500 error page by default and otherwise suppress the display of details. You need to configure a flag to send mail or register such exceptions at runtime in other ways:
http://flask.pocoo.org/docs/errorhandling/
If you want the runtime exception to appear on page 500 returned to the browser for development purposes, you need to enable debug mode in the jar. This is done by setting app.debug as True:
http://flask.pocoo.org/docs/config/?highlight=app%20debug
You should not have debug mode for the user facing the production system.
source share