Many thanks for your helpful posts - in the end I just changed a bit
of my code to work with 2.4, but this will come in handy for when I
finally make the upgrade.
Thanks again,
Nick
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to
you could do a pip freeze in your old install, then do a pip install
-r requirements in the new one. That would probably catch most things.
Alex
On Tue, Jun 8, 2010 at 9:50 AM, Bill Freeman wrote:
> Additionally, the .pyc files are version specific. IF you had no specific
>
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
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 wrote:
> Hi,
>
> I'm currently running Django on CentOS using the supplied Python
I haven't tried it. But, I wouldn't think so. It shouldn't be hard
to install Django for 2.6. I've never used CentOS. But, most of the
time, a version requirement means "at least". Of course, in the case
of Python 3, that would not be true.
On Tue, Jun 8, 2010 at 4:25 AM, Nick
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
6 matches
Mail list logo