First, Dan, thanks for the reply. Second, apologies for the long delay, but
sometimes the day job gets in the way. Third, I did as you suggested, but
Django 1.6.1 was NOT removed. My best guess is that the official
documentation instruction that pip would take care of this for me only
applies when going from one official release to another, not when going
from an official release to a development release, though of course it does
not say so explicitly.
pip did uninstall the 1.7 files from Python27/Scripts when I pointed it to
them directly. I should add at this point that at the time of my original
post, I did not realize that there were only 4 of them and that
django-trunk was in the intended virtualenv alongside 1.6.1.
However, pip would not only not uninstall django-trunk, it told me it
wasn't installed, never mind the folder sitting there. Even better, git
remove didn't work either. "Fatal: not a git repository"
So I deleted django-trunk the old fashioned way, through my OS. Then I
activated the virtualenv, reconnected to git, and got django-trunk and the
admin files where I expected them to be - in the virtualenv. When I saw
this in my terminal window:
Adding Django 1.7a2 to easy-install.pth file
Deleting C:\Envs\VE1\Scripts\django-admin.py
Installing django-admin-script.py script to C:\Envs\VE1\Scripts
I assumed that meant it was taking care of 1.6.1 at the same time it was
installing 1.7a2, as I understood the install instructions to say it would
do. But when I ran print(django.get_version()), I got 1.6.1!
Then I deleted both the django folder and the egg folder through Windows,
but when I ran get_version again, I STILL got 1.6.1! I don't see how that
is possible. There is another Django 1.6.1, but it is inside a DIFFERENT
virtualenv, and when I exited the Python interpreter, I was right back to
the VE I was working with. There is a django-admin in Python27, but when I
opened it, it explicitly said that it was 1.7a2! Now it also had a line of
code I didn't understand:
require('Django==1.7a2')
del require
What is this doing? Deleting a requirement as soon as it is created? I
don't understand.
Finally, I decided to runserver. The good news is that my site still works
as it did before. The bad news is I have no idea how or why. Runserver also
explicitly stated that it was running 1.6.1.
So, I guess I'll have to muddle along without migrations, which was the
whole point of this exercise in futility. But I sure would like to
understand what is happening here, if any of you wiser and more experienced
heads can enlighten me.
\
On Saturday, March 8, 2014 3:10:20 AM UTC-6, Malik Rumi wrote:
>
> I am going from 1.6.1 to 1.7a2, mostly to take advantage of the new
> migrations feature.
> I followed the directions here
> http://django.readthedocs.org/en/latest/topics/install.html#removing-old-versions-of-django
>
> Since I originally installed with pip, supposedly that would take care of
> removing the old version for me if I installed with pip now.
> I changed into the subdirectory where 1.6.1 is, which is inside
> virtualenvwrapper.
> The commands they gave ran and reported success. However, 1.7a2 has been
> installed at Python27/Scripts, not inside my virtualenv
> 1.6.1 seems to alive and well at its same original location.
> What do I now? Can I just delete the 1.6.1 folder? Will pip/virtualenv
> know where to find 1.7a2 for my cuurent projects? Should I start the
> install over?
> Thx.
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/64ea91d3-f4df-470d-bad2-9c818708cb3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
