> On 6 Sep 2016, at 4:56 AM, Roger Wayne <[email protected]> wrote:
> 
> What was the exact pip command you used? Want to know whether you used the 
> URL location from the Internet, or copied the file to local disk and tried to 
> install it from there. Provide the actual command can so see.
> 
> "pip install mod_wsgi" I downloaded it to my hard drive and tried to install 
> it from there.
> 

Running ‘pip install mod_wsgi’ will always try and install mod_wsgi from source 
code downloaded from PyPi. This installation method is not supported on Windows.

Even if you installed the .whl file the correct way using pip, it installs it 
off in some directory in the Python installation. You would have to have found 
where it was installed and copied it into the Apache modules directory, or Use 
the full path to where it was installed in the LoadModule line.

How to do that is not documented at all by the person who makes those .whl 
files available. I am surprised anyone can work out what to even do with them.

> The .whl file is a zip file is what I meant. So download from pythonlibs site 
> and change extension from .whl to .zip if necessary and then unpack it.
> 
> You really want to avoid trying to compile it yourself as getting the right 
> compiler is a pain. For Python 3.5 there are no instructions for how to get 
> the corresponding compiler. They use different compiler to what 3.4 and 
> before used.
> 
> But what mod_wsgi binaries were you using? That is why I think I already 
> asked which you downloaded. That is, what was the actual name of package 
> pulled down. They have architecture and version information in names. You 
> have to use the correct one.
> 
> "mod_wsgi-4.4.23+ap24vc10-cp34-cp34m-win32.whl" but I also tried 
> "mod_wsgi-4.4.23+ap24vc14-cp35-cp35m-win32.whl" on Python 3.5 . Also I went 
> to the main github page and downloaded the zipped file mod_wsgi-4.5.5 I 
> believe.
> 

What is on the GitHub page is of no use really again as you likely want to 
avoid compiling from source code.

What you should have done is take the .whl file for whatever Python version you 
want to use, and change the .whl extension to .zip. Then use a zip unarchiver 
to extract the .so file out of it and copy it into your Apache modules 
directory. Did you do that?

> Am really surprised you would be using 32 bit. You would generally want to be 
> using 64 bit these days.
> 
> Xampp was only available in 32-bit (for Windows) and as you stated before, 
> everything has to be 32 or 64 bit. I tried out Wamp (it is available in 
> 64-bit) but Xampp was more user friendly to me. Do you really think it is a 
> good idea to be using 64 bit? I would say performance-wise, it would make a 
> great deal of a difference but I don't know how much that difference would be.
> 
> The errors in log are because you are trying to run stuff as CGI scripts and 
> also because you are using Python 2 code and not Python 3 code. The way that 
> ‘print()’ is used differs.
> 
> This is where I am confused. My code in the CGI scrips is Python 3 code. I 
> ran it through the compiler for Python, and I only have version 3. I was 
> definitely lost when i saw that error because my compiler was saying that my 
> code was good to go yet the error log said I had a syntax error. But now that 
> you brought it up, Python 2 uses print without parenthesis. It still is 
> strange because everything I have gotten so far were versions for Python 3, 
> so Python 2 shouldn't even be a factor. At least I don't think. I attached 
> the code that it was complaining about in case you wanted to check it out for 
> yourself. But you are saying the extension should be .py instead of .cgi, , 
> right? I thought it did not matter what the extension was but having the .py 
> extension would make sense.
> 
> 
> Thanks for sticking with me so far.
> 
> -- 
> 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] 
> <mailto:[email protected]>.
> To post to this group, send email to [email protected] 
> <mailto:[email protected]>.
> Visit this group at https://groups.google.com/group/modwsgi 
> <https://groups.google.com/group/modwsgi>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> <tasteful.cgi>

-- 
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.

Reply via email to