> On 24 Mar 2016, at 5:34 PM, Jaqen Nki <[email protected]> wrote:
>
> Ok so my issue was on ./configure I entered
> --with-python=/usr/local/lib/python3.4 rather than just python3. I deleted
> flask from system python, and left flask installed into python3 - it now
> serves the page properly! My venv is using 3.4. The vhost flask app is
> working fine. this line in the .wsgi file makes me curious though:
If giving full path, and it was in /usr/local/bin, would have been:
./configure --with-python=/usr/local/bin/python3.4
That is, path to Python executable, not the library directory.
Using ‘python3’ meant it would have used whatever was found in your PATH, which
I presumed is what you wanted.
>
> #!/usr/bin/python
>
> Would this shebang line call the python2.x to run the .conf and .wsgi files.
> Dont see how it could matter because apparently the app is running fine with
> 3.4. Anyways thanks.
The #! line in a WSGI script file is not relevant. You generally do not include
it in a WSGI script file.
It is not needed because mod_wsgi is compiled against and links to a specific
Python version/installation and that is what dictates what is used.
Graham
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
