Great! Thanks!
No idea how im gonna do that since i have no idea where/how to get
that source code and do it, but at least i know what to do.
Alan.
On Aug 17, 1:44 am, Graham Dumpleton
wrote:
> On Aug 16, 10:43 pm, zayatzz wrote:
>
> > apparently installing mod_wsgi was not the instant get ou
On Aug 16, 10:43 pm, zayatzz wrote:
> apparently installing mod_wsgi was not the instant get out of trouble
> card.
>
> For a while i had problem with mod_wsgi settings. Now the trouble with
> modules continues. I think i must somehow finally fix all the paths.
>
> current error is :
> [Sun Aug
apparently installing mod_wsgi was not the instant get out of trouble
card.
For a while i had problem with mod_wsgi settings. Now the trouble with
modules continues. I think i must somehow finally fix all the paths.
current error is :
[Sun Aug 16 12:38:22 2009] [error] [client 127.0.0.1] rai
z...@zayatzz:/var/log/apache2$ ls -las /usr/local/lib/python2.6/site-
packages
total 27
0 drwxrwsr-x 3 root staff 144 2009-08-16 12:09 .
19 drwxrwsr-x 26 root staff 19392 2009-08-16 10:54 ..
1 drwxr-sr-x 17 root staff 496 2009-08-16 12:09 django
4 -rw-r--r-- 1 root staff 947 2009-08-16
On Aug 16, 9:24 pm, zayatzz wrote:
> I did reinstall mod_python indeed.
Then you can't have installed it for that version of Python. Did you
use the --with-python option to 'configure' for mod_python to tell it
to use your alternate Python installation? That or the installed
mod_python is not
I did reinstall mod_python indeed.
when i do import mod_python then :
>>> import mod_python
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named mod_python
>>>
so nope :(
Alan
On Aug 16, 2:01 pm, Graham Dumpleton
wrote:
> Did you actually bother to rein
Did you actually bother to reinstall mod_python after you nuked your
original Python installation. Likely when reinstalling it you lost
everything that was in prior site-packages and so are missing the
Python module component bits of mod_python, ie., no longer installed.
If from command line stac
i begun to think about the same thing when i went through the log.
Couldnt find anything useful why mod_python is failing atm, so i
anyone can think of why this is not working - i still could use your
help. Otherwise since it has nothing to do with django, i'll try to
get help though stackoverflo
It looks like the issue is occurring when Apache tries to load mod_python.
This doesn't have anything to do with Django at this point. You may need to
do a bit more research on how Stackless Python works with Apache and
mod_python.
On Sun, Aug 16, 2009 at 5:04 AM, zayatzz wrote:
>
> apache err
Can you post your error log?
On Sun, Aug 16, 2009 at 4:12 AM, zayatzz wrote:
>
> Hello
>
> I installed stackless pyton 2.6.2 after reading several sites that
> said its fully compatible with vanilla python. After installing i
> found that my django applications do not work any more.
>
> I did
apache error log shows such stuff:
http://dpaste.com/81241/
Alan.
On Aug 16, 12:12 pm, zayatzz wrote:
> Hello
>
> I installed stackless pyton 2.6.2 after reading several sites that
> said its fully compatible with vanilla python. After installing i
> found that my django applications do not wo
Hello
I installed stackless pyton 2.6.2 after reading several sites that
said its fully compatible with vanilla python. After installing i
found that my django applications do not work any more.
I did reinstall django (1.1) again and now im kind of lost. The error
that i get is 500:
Internal Se
12 matches
Mail list logo
