On Nov 4, 2009, at 4:01 AM, joker wrote:
>
> i update python 2.5.2 to 2.6 and setup changed directory
> /usr/lib/python2.5 to /usr/local/lib/python2.5/
That doesn't look right. If you installed 2.6, the new directories
should have 2.6 in them, not 2.5 and so should your tracebacks.
S
> a
i worked easy_install mysql-python command but still doesnt work
On 4 Kasım, 11:17, Roland van Laar wrote:
> joker wrote:
> > i update python 2.5.2 to 2.6 and setup changed directory
> > /usr/lib/python2.5 to /usr/local/lib/python2.5/
> > and django doesnt working now
>
> > ImproperlyConfigured
joker wrote:
> i update python 2.5.2 to 2.6 and setup changed directory
> /usr/lib/python2.5 to /usr/local/lib/python2.5/
> and django doesnt working now
>
> ImproperlyConfigured: Error importing middleware
> django.contrib.flatpages.middleware: "No module named mysql.base"
>
You might want t
Looks like your python 2.5 had the python mysql packages installed, but
your new python 2.6 doesn't, which it wouldn't being a fresh install.
Now you need to install the python mysql bindings into python 2.6.
Also, you should probably have your libs in for python 2.6
in /usr/local/lib/python2.6/
i update python 2.5.2 to 2.6 and setup changed directory
/usr/lib/python2.5 to /usr/local/lib/python2.5/
and django doesnt working now
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line
1537, in HandlerDispatch
File "/usr/lib/python2.5/s
5 matches
Mail list logo
