[mod_python] Windows Server 2008

Michael Johnson donothurry at gmail.com
Thu Jan 22 15:45:19 EST 2009


Hi Tim,

Yes, I ran the .py Hello World application like you suggested.  So
mod_python is definitely working on W 2008.

You are correct that Django offers a development-only server that by
default runs on port 8000.  Now I can use either the Django Web server
or Apache.

Thanks,
Mike

On Thu, Jan 22, 2009 at 3:29 PM, Tim Valenta <tonightslastsong at gmail.com> wrote:
> I don't think Django makes use of mod_python until you move into
> 'production' mode, though... it's development server is internally run by
> just django code (I think).  If you've got apache set up already, and you
> think you've got mod_python in place (including the Apache directive to your
> web root, with something like the standard mod_python.publisher handler),
> the true test would be to write up a small .py file with a "def index(req):"
> and something like "req.write('hello world')" in the body.  Then if it runs,
> you'll know mod_python is working :)
>
> On Thu, Jan 22, 2009 at 1:01 PM, Michael Johnson <donothurry at gmail.com>
> wrote:
>>
>> Mod_python works for me now on Windows Server 2008 Standard Edition
>> for 32-bit systems.
>>
>> The Windows .msi installer for mod_python stops working near the end
>> of the installation when the clean-up script begins.  But enough of
>> the code is loaded apparently and I am running a Python Django site
>> successfully on Windows 2008 Server Release 2.
>>
>> Mike
>>
>>
>>
>> On Fri, Jan 16, 2009 at 11:53 PM, Tim Valenta
>> <tonightslastsong at gmail.com> wrote:
>> >> Those which which integrate quite closely with mod_python
>> >> specific handlers probably more so than those which use a minimal API
>> >> such as a WSGI bridge.
>> >
>> > Hence your suggestions to me before, to choose a platform which
>> > abstracts itself a bit more, like whole WSGI thing. <offtopic>  You've
>> > got some good blog entries, by the way </offtopic>.  For the record, I
>> > kind of like Django.  I originally wrote it off as 'too big' for my
>> > interests, but I've given it another chance and it's quite nice.  And
>> > since it's open source, contributions will keep it alive well into
>> > Python's future versions, in my opinion.  But, the mod_python mailing
>> > list isn't necessarily the place for Django talk.
>> >
>> > Tim
>> >
>> > On Fri, Jan 16, 2009 at 7:22 PM, Graham Dumpleton
>> > <graham.dumpleton at gmail.com> wrote:
>> >> 2009/1/17 Tim Valenta <tonightslastsong at gmail.com>:
>> >>> Actually, I'm realizing an issue on my end-- I don't think mod_python
>> >>> has a
>> >>> 64-bit flavor, and my installation of WS 2008 is 64-bit.  Even if I
>> >>> got an
>> >>> x64 Python and Apache setup running, I'd be lacking the mod_python to
>> >>> power
>> >>> the test.
>> >>> Sorry!  mod_python's apparently been lagging behind the modern 64-bit
>> >>> option, and doesn't have versions for the newest Python versions
>> >>> (Python 2.6
>> >>> and Python 3, both of which are still pretty new).
>> >>
>> >> Don't expect a Python 3.0 version, the C APIs aren't compatible and a
>> >> lot of work would need to be done to port mod_python to Python 3.0.
>> >> Even if was made to work, any applications on top would like need to
>> >> change. Those which which integrate quite closely with mod_python
>> >> specific handlers probably more so than those which use a minimal API
>> >> such as a WSGI bridge.
>> >>
>> >> Graham
>> >>
>> >>> Sorry I couldn't be of any help.  I'd only recommend trying some
>> >>> program
>> >>> compatibility options with Windows.  We may not see a direct fix very
>> >>> promptly.
>> >>> Tim
>> >>>
>> >>> On Fri, Jan 16, 2009 at 12:36 PM, Tim Valenta
>> >>> <tonightslastsong at gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> Windows Server 2008 is still really new... It wouldn't surprise me at
>> >>>> all
>> >>>> if there are things in it that break the installer.  I use Windows
>> >>>> Vista
>> >>>> without problems (of this nature).  I did install the trial WS
>> >>>> Hyper-V 2008
>> >>>> a few months back, perhaps I could boot into it and see If i have any
>> >>>> luck
>> >>>> during installation, but I couldn't guarantee anything.  I'll have to
>> >>>> check
>> >>>> it out tonight when I go home.
>> >>>> For reference's sake, I use the same versions of mon_python and
>> >>>> Apache as
>> >>>> you've described.
>> >>>> Tim
>> >>>>
>> >>>> On Fri, Jan 16, 2009 at 12:19 PM, Michael Johnson
>> >>>> <donothurry at gmail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> The installation program appears to successfully complete the Python
>> >>>>> portion but fails after the Apache location is selected.
>> >>>>>
>> >>>>> The message is the standard Windows message for programs that stop
>> >>>>> running.  The text is approximately:
>> >>>>>
>> >>>>> "mod_python-3.1.1.win32-py2.5-Apahce2.2.exe has stopped working for
>> >>>>> some reason.  Windows will now end the program."
>> >>>>>
>> >>>>> Thanks!
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Fri, Jan 16, 2009 at 1:50 PM, Tim Valenta
>> >>>>> <tonightslastsong at gmail.com>
>> >>>>> wrote:
>> >>>>> > What message does it fail with?
>> >>>>> >
>> >>>>> > On Fri, Jan 16, 2009 at 11:38 AM, Michael Johnson
>> >>>>> > <donothurry at gmail.com> wrote:
>> >>>>> >>
>> >>>>> >> On Windows Server 2008, the installation program for mod_python
>> >>>>> >> fails.
>> >>>>> >>  Does anyone have a fix?  Thanks!
>> >>>>> >>
>> >>>>> >> mod_python-3.3.1.win32-py2.5-Apache2.2.exe
>> >>>>> >> _______________________________________________
>> >>>>> >> Mod_python mailing list
>> >>>>> >> Mod_python at modpython.org
>> >>>>> >> http://mailman.modpython.org/mailman/listinfo/mod_python
>> >>>>> >
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Michael L Johnson
>> >>>>> w: 978-281-9300 x 6521
>> >>>>> c: 978-290-9005
>> >>>
>> >>> _______________________________________________
>> >>> Mod_python mailing list
>> >>> Mod_python at modpython.org
>> >>> http://mailman.modpython.org/mailman/listinfo/mod_python
>> >
>>
>>
>>
>> --
>> Michael L Johnson
>> w: 978-281-9300 x 6521
>> c: 978-290-9005
>
>
>
> --
> i was not declared before this scope.
>



-- 
Michael L Johnson
w: 978-281-9300 x 6521
c: 978-290-9005


More information about the Mod_python mailing list