Seeing as that there will be backwards incompatible changes coming in future releases of Django I installed 0.96 in my environment today. I simply ran setup.py and the libraries were put in the appropriate site-packages directory. The new version seemed to get picked up:
>>> import django
>>> django.VERSION
(0, 96, None)
The release notes mention an additional view for adding users in admin. It didn’t seem to exist for me. It seemed like the old 0.95.1 library I was using was being picked up in this instance, so I removed the egg package for it and all seemed well.
It turns out that the problem was that the older 0.95.x packages used setuptools where the new one doesn’t. The new install didn’t create an egg package and the reference to the old one still existed in the easy-install.pth file in my site-packages:
$ cat easy-install.pth
import sys; sys.__plen = len(sys.path)
./setuptools-0.6c5-py2.5.egg
./Django-0.95.1-py2.5.egg
./vobject-0.4.8-py2.5.egg
./python_dateutil-1.1-py2.5.egg
./flup-0.5-py2.5.egg
./MySQL_python-1.2.2-py2.5-macosx-10.3-i386.egg
import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new)
Simply removing the reference to Django-0.95.1-py2.5.egg will also do the trick.
Hey,
Thanks for that tip, trying to get it to recognise 0.96 was becoming a headache! Now if only i can get freecomments working…