when I pip-installed django-debug-toolbar, the latest version of Django was installed automatically.

563 views
Skip to first unread message

jmin...@gmail.com

unread,
Feb 17, 2014, 2:41:07 PM2/17/14
to django...@googlegroups.com
Hello,

when I pip-installed django-debug-toolbar, the latest version of Django was installed automatically. Not my intention. I got warning as below.


    ========
    WARNING!
    ========

    You have just installed Django over top of an existing
    installation, without removing it first. Because of this,
    your install may now include extraneous files from a
    previous version that have since been removed from
    Django. This is known to cause a variety of problems. You
    should manually remove the

    /usr/local/lib/python2.7/site-packages/django

    directory and re-install Django.




but never asked if it is OK to do so. So, I tried to uninstall it and reinstall it. Wehn I do
rm -rf django
pip install django==1.3
somehow, it says,


Requested django==1.3, but installing version 1.6.2
Installing collected packages: django
  Running setup.py install for django


Again version 1.6 was installed. Does anyone know the solution to it. Please.


Jun

Frank Bieniek

unread,
Feb 17, 2014, 3:01:53 PM2/17/14
to django...@googlegroups.com
Hi,

pip install --no-deps django-debug-toolbar
might help. --no-deps = no dependencies

I highly recommend you pip freeze
your current environement and then just do a pip install --no-deps
new_component_name,
thisway you know what is in your environment and no component can seek
stuff in...

hope this helps
Frank

http://pip.readthedocs.org/en/latest/user_guide.html#configuration
> --
> 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...@googlegroups.com.
> To post to this group, send email to django...@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/a571e1ed-88e1-4263-b288-b34837fd9a80%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

jmin...@gmail.com

unread,
Feb 17, 2014, 3:21:11 PM2/17/14
to django...@googlegroups.com
Hi Frank,

Thank you for your advice but the version is still 1.6. I straggle with getting it back to the version 1.3.
pip install --no-deps django-debug-toolbar 
may help when the version become 1.6, right?


by the way, I tried
pip install --no-deps django==1.3
did not help

Jun

2014年2月18日火曜日 5時01分53秒 UTC+9 Frank Bieniek:

Frank Bieniek

unread,
Feb 17, 2014, 7:17:13 PM2/17/14
to django...@googlegroups.com
Hi Jun,
to get your old django back
1) pip uninstall django
2) pip install django==1.3
3) pip uninstall django-debug-toolbar
4) pip install --no-deps django-debug-toolbar

line 1 - remove existing django whatever version
line 2 - install django 1.3
line 3 - remove the django toolbar
line 4 says: install django-debug-toolbar but ignore all dependencies of this package.

This should cleanup your environment
Cheers
Frank




Am 17.02.14 21:21, schrieb jmin...@gmail.com:

jmin...@gmail.com

unread,
Feb 18, 2014, 12:56:09 AM2/18/14
to django...@googlegroups.com
hi Frank,

I appreciate it but seem that this situation is so unusual  that people do not understand. 
I have done those already.


So I do 
1) pip uninstall django
3) pip uninstall django-debug-toolbar

2) pip install django==1.3



then it says:


Downloading/unpacking django==1.3
  Running setup.py egg_info for package django

    warning: no previously-included files matching '__pycache__' found under directory '*'
    warning: no previously-included files matching '*.py[co]' found under directory '*'
  Requested django==1.3, but installing version 1.6.2
Installing collected packages: django
  Running setup.py install for django

then the version 1.6 is installed. Any solution?  





2014年2月18日火曜日 9時17分13秒 UTC+9 Frank Bieniek:

Charly Román

unread,
Feb 18, 2014, 1:21:35 AM2/18/14
to django...@googlegroups.com

Latest django-debug-toolbar isn't compatible with django 1.3

jmin...@gmail.com

unread,
Feb 18, 2014, 1:34:56 AM2/18/14
to django...@googlegroups.com
Hi Charly,

But django-debug-toolbar is uninstalled. How does that affect? Please.

Jun

2014年2月18日火曜日 15時21分35秒 UTC+9 Charly Román:
Message has been deleted

donarb

unread,
Feb 18, 2014, 10:44:08 AM2/18/14
to django...@googlegroups.com
What version of Python are you running? Django 1.3 runs with Python 2.4. I'm not sure, but maybe a higher version of Python is triggering a higher version dependency of Django.

If you want to install Django 1.3, you should probably do it in a virtualenv, after installing Python 2.4. 

Xavier Ordoquy

unread,
Feb 18, 2014, 10:50:51 AM2/18/14
to django...@googlegroups.com

On Monday, February 17, 2014 9:56:09 PM UTC-8, jmin...@gmail.com wrote:
hi Frank,

I appreciate it but seem that this situation is so unusual  that people do not understand. 
I have done those already.


So I do 
1) pip uninstall django
3) pip uninstall django-debug-toolbar

2) pip install django==1.3



then it says:


Downloading/unpacking django==1.3
  Running setup.py egg_info for package django

    warning: no previously-included files matching '__pycache__' found under directory '*'
    warning: no previously-included files matching '*.py[co]' found under directory '*'
  Requested django==1.3, but installing version 1.6.2
Installing collected packages: django
  Running setup.py install for django

then the version 1.6 is installed. Any solution?  


Depending on how old your pip version is, you may need to clean up things in your /tmp.
I have faced similar issues with old pip versions. It happened when an installation failed and left temporary package files in /tmp. Whatever the version you’ll want to install, it’ll take the one on the /tmp and will not remove it by itself.

The correct workaround is to clean /tmp and try a new installation.

Regards,
Xavier Ordoquy,
Linovia


Reply all
Reply to author
Forward
0 new messages