Additionally, the .pyc files are version specific. IF you had no specific incompatibilities, you could consider deleting all .pyc files in the copy, then import every .py file running as root, to make new .pyc files.
But then there are likely to be plenty of other issues anyway, as Alex points out. This is all much more work than just installing stuff fresh, in these bold new days of distribute and pip install. Bill On Tue, Jun 8, 2010 at 10:32 AM, Alex Robbins <[email protected]> wrote: > You don't want to just copy site-packages. If you have any compiled > modules (pyyaml, PIL, etc) they won't work, since they were compiled > for the old version of python. > > Alex > > On Jun 8, 4:25 am, Nick <[email protected]> wrote: >> Hi, >> >> I'm currently running Django on CentOS using the supplied Python 2.4. >> I now need to use Python 2.6. I have installed Python 2.6 from the >> EPEL repositories, which sits alongside 2.4 (which is required for >> CentOS things such as "yum"). >> >> Django (and other Python modules) are all located in Python 2.4's site- >> packages folder. When I upgrade to 2.6, is it just a case of copying >> these over into 2.6's site-packages folder, or do I need to install >> the modules afresh? >> >> Thanks, >> Nick > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
