Thank you for doing the Windows build.

It is not that hard if you know how to access Windows Registry.

Under the Registry key named

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App 
Paths\Python.exe]

If this key exist, Python is installed. Then, for the actual path, you 
look at the value corresponding to this key; it should be something like:

"C:\Program Files\Python\Python.exe"

Once you find the path, it is best to check and make sure that 
'Python.exe' does exist in that path.

If all these are in place, you can go ahead with install. If not, you 
may want to warn/remind the user to install Python --and exit.

Incidentally, I have no idea whether 32-bit/64-bit Python is important 
for Cherokee. Nor do I know how to determine whether the current Python 
installation is 32-bit or 64-bit.

BTW, I am assuming you built a Win32 version; are by any chance planning 
to do Win64 too --so I thought I might as well look a gift horse in the 
teeth <VBG>.


On 2008-11-08 06:51, Stefan de Konink wrote:
> It is hard for some people to understand that there are other platforms
> then Linux. Indeed, they are less stable, have a more `experimental'
> setup and basically lack the tools to do your daily job. But ok, Windows
> comes for free with your PC, so why pay for something different, your
> boss may have asked.
>
> We understand you cannot miss mission critical applications, running on
> IIS just does not work for you, mainly because it does not work for
> anyone. You need to get back that `killer performance'.
>
>
> Especially for you, our beloved users, we developers united. And tried
> to rebuild something that allows you to do your job. And your computer
> show what it is really worth, also in environments that are hostile.
>
> If you are eager to check out the beta branch of Cherokee, an updated
> win32 binary is available;
>
> http://kinkrsoftware.nl/contrib/cherokee/cherokee-win32.zip
> Unzip it to C:\www
> Double click on cherokee-worker.exe
>
> And basically you have your shiny new IIS^H^H^H Cherokee Webserver
> running. [You might have to click 'unblock']
>
>
>
> There are some issues regarding compilation, path handling and pthreads
> we need to fix, so don't start your benchmarks just yet ;) The
> cherokee-admin is for obvious reasons not available, nor is a fcgi-php
> for win32. Before I forget, visuals are attached!
>
>
> Since I'm now officially bounded to the GPL, I can tell you that all
> files where compiled using the latest SVN, and use some code fixes that
> are probably integrated into the next revision log :)
>
>
> Have fun,
>
> Stefan
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Cherokee mailing list
> [email protected]
> http://lists.octality.com/listinfo/cherokee
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to