|
Tim Valenta
tonightslastsong at gmail.com
Fri Jan 16 23:53:32 EST 2009
> 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
|