Skip to main content
Stack Overflow
  1. About
  2. For Teams

Timeline for ipython reads wrong python version

Current License: CC BY-SA 3.0

25 events
when toggle format what by license comment
Jul 15, 2021 at 9:10 answer added Sahil Patel timeline score: 0
Apr 20, 2021 at 19:46 answer added Love and peace - Joe Codeswell timeline score: 0
Mar 15, 2019 at 0:11 answer added sh87 timeline score: 57
Mar 13, 2019 at 5:32 answer added Gru timeline score: 0
Jan 12, 2018 at 9:33 answer added Johnny timeline score: 6
Oct 30, 2017 at 22:28 answer added Jeremy Paige timeline score: 0
Jun 15, 2017 at 2:21 answer added Harish Kayarohanam timeline score: 0
Jun 9, 2017 at 23:29 answer added Mad Physicist timeline score: 1
Dec 18, 2016 at 18:25 answer added parsethis timeline score: 3
Sep 23, 2016 at 11:40 answer added Avikd timeline score: 1
Dec 17, 2015 at 10:12 answer added pvieytes timeline score: 10
S Oct 7, 2015 at 19:54 history suggested abcd CC BY-SA 3.0
fix some things
Oct 7, 2015 at 19:24 review Suggested edits
S Oct 7, 2015 at 19:54
Jul 31, 2012 at 3:10 vote accept Diego-MX
Jul 31, 2012 at 3:10 vote accept Diego-MX
Jul 31, 2012 at 3:10
Jul 31, 2012 at 3:07 vote accept Diego-MX
Jul 31, 2012 at 3:07
Apr 30, 2012 at 10:16 answer added Manuel Ebert timeline score: 158
Feb 23, 2012 at 18:32 comment added millimoose Libraries work the same. If you installed numpy etc. after installing Python 2.7.2 from source, they were likely installed into the 2.7.2 directory. This means that the Python 2.7.1 version wouldn't see those libraries at all. Since IPython was installed with 2.7.1, it couldn't see those libraries either. Basically, you can have as many completely separate copies of Python on your system as you want, but it can be hard keeping track of which one is used for what. Unless you know what you're doing, it's best to start with the built-in version of Python, and just reinstalling missing libraries
Feb 23, 2012 at 18:24 comment added millimoose Essentially, when you install any python "program", like IPython or even easy_install, the startup script for the program is set to always use the python executable it was installed with. So, if you had Python 2.7.1 without your libraries, and then install IPython, IPython is installed "into" the Python 2.7.1 installation, and a link to the ipython executable is placed on your PATH. If you then install Python 2.7.2 from source, it's a new, separate copy of Python it won't upgrade the existing 2.7.1 that has IPython in it. So IPython won't see the 2.7.2 copy, or any libraries in it.
Feb 23, 2012 at 15:19 comment added Diego-MX Okay, so I think my problem got fixed, as now iPython runs with the right version of Python which is 2.7.2 instead of 2.7.1. I think this got fixed when using easy_install but wasn't working well when installing it with pip. Is this correct? Could you tell me a little bit about how IPython startup works, so that I can take something from this? Regards
Feb 22, 2012 at 18:27 comment added millimoose Specific about which part? How IPython startup works, or how to make the problem go away?
Feb 22, 2012 at 13:57 comment added Diego-MX Could you be more specific?... thanks
Feb 21, 2012 at 22:17 comment added millimoose The ipython script is "tied" to the specific Python version it was installed with – it won't automatically switch to what you installed last. If you first installed 2.7.1, then IPython, then 2.7.2 from source, your IPython will keep using 2.7.1. You need to either undo all your flailing, go back to your original Python version and figure out what the reason was behind point 1; alternately, reinstall IPython using whichever Python install can access the libraries you need.
Feb 21, 2012 at 22:15 answer added macduff timeline score: 6
Feb 21, 2012 at 22:11 history asked Diego-MX CC BY-SA 3.0
toggle format

AltStyle によって変換されたページ (->オリジナル) /