If django was installed somewhere like /usr/lib/python2.5/... then, yes, the
new python install won't have access to it. That would be if you used
pip, eacy_install, or python setup.py as root to install it, and didn't give
any special arguments to install it elsewhere.
It's probably best to reinstall with the new python anyway, since there can
be dependencies that vary based on python version. Note that the .pyc
files in you project are only compatible with one version. 2.7 might deal
with this for you automatically, but it is probably best to remove them and
let 2.7 build its own.
2.7, IIRC, comes with sqlite, but if you are using, say, psycopg2 or mysql,
you will probably need to install the python packages for that as well.
The underlying lib files and DB installation should be fine as they are.
Bill
> --
> You received this message because you are subscribed to the Google Groups "Django users" group.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to django-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
>
>