New django app fails with "Premature end of script headers: wsgi.py"

I just created a new django app in the webfaction control panel, using the latest, python3.3 and django 1.6 pair.

This creates an Apache server with mod_wsgi 3.4 and Python 3.3 installed running Django 1.6.

I've tested via runserver locally (created initially via django 1.6's startproject) and runs fine. I've posted my app to server, and testing with python3 and the shell, and runserver the app appears to load and models import without issue.

It's only when I try to actually access the page (no change after restarting apache) Checking my ~/logs/user/myapp_error.log I see the following:

[Tue Dec 10 13:53:46 2013] [error] [client 127.0.0.1] Premature end of script headers: wsgi.py

[Tue Dec 10 13:53:47 2013] [notice] child pid 25586 exit signal Segmentation fault (11)

The strange thing is that running a test wsgi hello world program gives me no issues:

import sys

def application(environ, start_response):
    status = '200 OK'
    output = 'Hello World!'

    response_headers = [('Content-type', 'text/plain'),
                        ('Content-Length', str(len(output)))]
    start_response(status, response_headers)

    print('sys.prefix = {}'.format(repr(sys.prefix)), file=sys.stderr)
    print('sys.path = {}'.format(repr(sys.path)), file=sys.stderr)

    return [output]

I haven't added or changed anything in myapp/apache2/conf/httpd.conf other than to adjust the paths to myapp name. Note I have installed python3 libraries into ~/webapps/myapp/lib/python3.3, but like I said it's importing fine outside of apache.

If I had some kind of traceback to work with I could probably figure this out, but I'm stuck. It seems that many mod_wsgi Segfault issues point to compilation linking errors with apache/mod_wsgi, but that's something I don't have control over...

Any ideas on how to proceed with this would be helpful.