Building + unit testing :
* mod_python on Windows 2000 Server SP4 + ActivePython 2.3.5 + Apache 2.0.55
* mod_python on Windows XP SP2 + ActivePython 2.4.2 + Apache 2.0.55
Developing (mod_python itself + my own applications):
* mod_python on Windows XP SP2 + ActivePython 2.4.2 + Apache 2.0.55
Production servers :
* mod_python on Windows 2000 Server SP4 + ActivePython 2.4.1 +
Apache 2.0.55
Yes that's a weird production setting but :
1) I need MS SQL Server 2000 and its nice & cheap OLAP extensions.
2) I love Python
3) I still have to maintain some applications running under PHP
4) I need to have a single server which handles PHP, SVN and
mod_python so Apache is a must, I cannot use IIS
Regards,
Nicolas
I'm using mod_python for Python 2.4 on Windows XP for developement, and on Win
2006/1/19, Jorey Bump <[EMAIL PROTECTED]>:
> Mike Looijmans wrote:
>
> > Seriously, I think Grisha's way is right - the three musketeers should
> > decide based on the feedback they get. There's no substitute for running
> > on other people's machines...
> >
> >> 2006/1/19, Gregory (Grisha) Trubetskoy <[EMAIL PROTECTED]>:
> >>
> >>> Thanks Roy. Very timely, since 3.2.6 is (so far) going to be a
> >>> final/stable release.
> >>>
> >>> I propose that for starters those people are:
> >>>
> >>> me (I'm also in the Apache HTTP Server PMC)
> >>> Jim Gallacher
> >>> Nicolas Lehuen
> >>> Graham Dumpleton
>
> +1 here, but since the build process and typical MPM differs among
> platforms, could we see a list that this group represents? I'm most
> interested in default nonvirtualized environments used in production or
> for principal development. This information will be useful when
> reviewing release candidates, to make sure we haven't overlooked any key
> platforms.
>
> IOW, could you guys list the OS on which you run, and not merely test,
> mod_python?
>
