[pycsw-devel] Running on Windows

[Tom Kralidis]

I'm not familiar with Windows environments for Apache/mod_wsgi
setups, so you'll have to check with those mailing lists for more
information.  It would be valuable to see if / how this works on Windows,
so do let us know of any progress.  Good luck!

..Tom


On Sun, Nov 18, 2018 at 3:51 PM Tim Wanner <tim_wanner at web.de> wrote:
>
> Hi Tom,
>
> Yes this will help. Thanks! So I got my python 2.7.13 installed in C: \Python27\Python that should do.
>
> About the mod_wsgi: yes if considered this and will try to manage it. Running with python 2.7 + mod_wsgi for Apache conf. turns out to be very tricky (till impossible) as told on: https://github.com/GrahamDumpleton/mod_wsgi/blob/master/win32/README.rst
> ‚Python 2.7 is compiled with VC9‘
>
> "The problem is that Apache Lounge, whose Apache binaries have been used up until this point, has stopped making available versions of Apache compiled with a VC9 compiler.
> This means that if you hadn't managed to download a Win32 VC9 version of Apache at some time in the past, you technically can't use mod_wsgi on Windows with Python 2.6 or Python 2.7 any more as you can't get the right version of an Apache binary“
> 'The actual mod_wsgi binaries that are made available are:
>
> Apache22-win32-VC9/modules/mod_wsgi-py27-VC9.so
>
> Apache24-win32-VC9/modules/mod_wsgi-py27-VC9.so
>
> Those labelled with Apache22-win32-VC9 should be used with an Apache 2.2 Win32 VC9 version of Apache. Alas Apache Lounge no longer makes such binaries available any more.
> If you don't already have an older version of Apache which has been compiled with the Win32 VC9 compiler you are out of luck.’
>
> "Note that Apache Lounge never made available any Win64 VC9 binaries for Apache 2.4.
> This means that technically there is no combination available for correctly running mod_wsgi with a Win64 VC9 version of Python 2.6 or 2.7.“
>
> At this point I’m not sure weather I can go with a pip install mod_wsgi or if that turns out to fail? Which mod_wsgi will it generate ? Depense this on the python version I’ll use for pip command right ?
>
> So I’d go just with python 3.4 the whole lot as this is compiled with VC10 and there are fitting apache version available right ?
>
>
> Thank a lot for your response this will help me a lot.
>
> Tim
>
> Am 18.11.2018 um 14:53 schrieb Tom Kralidis <tom.kralidis at gmail.com>:
>
> Hi Tim:
>
> On Sun, Nov 18, 2018 at 6:34 AM Tim Wanner <tim_wanner at web.de> wrote:
>
>
> Hello Mailing List,
>
> this might be a 'beginner' question, but I couldn’t find a right description browsing the web and wanted to get this right in my Thesis.
>
> As the pycsw doc tell’s you’ve got to change line 1 of csw.py into : #!/python27/python -u, bevor installation of pycsw on windows and running it on there.
>
> Is this pointing to a UNIX (‚Ubuntu‘) directory somewhere external based to config the CGI handler and not to the Python version installed on the local windows computer ? (Win directory should be C:/python27/python.exe)
>
>
> As per http://docs.pycsw.org/en/stable/installation.html#running-on-windows ,
> the example assumes you have Python in \Python27\python .  The drive letter
> would be required if you are running if Python and your Python CGI script are
> on different paths.  Also note the -u flag for Windows environments
> (https://docs.python.org/3.3/using/cmdline.html#cmdoption-u)
>
> Having said this, have you considered running Python on mod_wsgi instead
> of CGI?  Many/most Python apps benefit from using mod_wsgi as a long
> running process for performance.
>
> Hope this helps.
>
> ..Tom
>
>
> Or is this just a expression form where under windows apache searches for the python dir. self-sufficient where python is stored for running the CGI Wrapper ?
>
> I would be pleased about a short background explanation.
>
> Thanks for your response
> Best Regards
>
> Tim
> _______________________________________________
> pycsw-devel mailing list
> pycsw-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pycsw-devel
>
>