Cool, thanks. I guess I will have to start using virtualenv, it came installed with my vps stack script, but I disabled it as I was having probs using postgres. I guess I never gave it a great deal of time.
I just dont get why its now reverted to v1.1, its not even on my python path, print sys.path shows only djangov1.2.egg on there...... Frustrating. Rob On Sep 17, 1:04 pm, Piotr Zalewa <zal...@gmail.com> wrote: > Hi Robbington. > > I'd suggest to use virtualenv and keep to use *only* pip > that way only you have the power to change anything > to update Django to a version above 1.2 simply > pip -E your_virtual_environment install Django>=1.2 > > zalun > > On 09/17/10 13:02, Robbington wrote: > > > > > > > Hey, > > > I keep getting this annoying problem that when I download and install > > a new django package, say django-registration it reverts django from > > version 1.2 to 1.1... Is there anyway to avoid this as it messes up my > > databases each time for each django project I am running. > > > I've used a variety of methods for getting these packages, > > easy_install, aptitude install, pip install all of the seem to do it.. > > > And does any one know the best way to upgrade django back to version > > 1.2, do I have to delete it and start again? > > > Thanks > > > Rob > > -- > blog http://piotr.zalewa.info > jobs http://webdev.zalewa.info > twit http://twitter.com/zalun > face http://facebook.com/zaloon- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
