[IPython-dev] Issue with upgrading from 0.6.15 to 0.7.0 via easy_install

[Robert Kern]

Fernando Perez wrote:
> Hi all,
> 
> this is a plea for help, hoping others on the list can bail me out on this 
> problem.  I don't have a clue.  I am forwarding Travis' message unmodified, in 
> the hope that somebody who knows about eggs can help us a little here.
> 
> [ Travis, thanks for 'doing the right thing and filing  a proper bug report. 
> In this case, however, I'm going to have to move this to the -dev list, 
> because I'm out of my league on this problem, so I need to enlist the help of 
> others who may have some ideas.  I've whitelisted you on the -dev list so your 
> posts don't bounce.  You still may want to subscribe to get the replies. ]
> 
> 
> I added egg construction as part of 0.7.0 mostly to satisfy user requests, but 
> I have to admit that my experiences with the system haven't been the best, so 
> a) I don't really know how to help here b) I'm not terribly interested in 
> learning any more about eggs.  I find the system unpleasant to use and to 
> cause (in IPython's case, I know there are contexts where it's indispensable) 
> more problems than it solves.  If providing ipython in egg format continues to 
> create hassles to users (and to myself) I may just discontinue the practice. 
> So far eggs have cost me quite a few hours, with no discernible benefit (kind 
> of like win32, but that's a monopoly I can't really fight ;-)
> 
> 
> Cheers,
> 
> f
> 
> =========================================================================
> Subject:Issue with upgrading from 0.6.15 to 0.7.0 via easy_install
> From:Travis Caldwell <travis_caldwell2000 at yahoo.com>
> Date:Wed, 11 Jan 2006 18:53:54 -0800 (PST)
> To:ipython-dev at scipy.net
> 
>   Hi,
> 
>   I had installed Ipython 0.6.15 via easy_install and that was working
> great.
> 
>   I then did a 'easy_install -U ipython' and it went out grabbed the new
> egg and did the install.
> 
>   Everthing looked great untill I tried to run Ipython and then I
> noticed that it was still running the previous 0.6.15 version.
> 
>   I initially thought that this was a path or script installation issue,
> but it looks like some of the setuptools magic is going wrong.
> 
>   The new ipython script that got installed in bin is basicly:
> 
> __requires__ = 'ipython==0.7.0'
> import pkg_resources
> pkg_resources.run_script('ipython==0.7.0', 'ipython')
> 
> 
> I know very little about easy_install or setuptools, but I read up on
> it a bit and tried to use pkg_resources.resource_string() to read out
> the script that gets run by run_script()
> 
> This may be user error with setuptools, but when I try this I get an:
> 
> ImportError: No module named ipython==0.7.0
> 
> Here a transcript of my session attempting to "manually" run Ipython:
> 
> pinky-1234% python2.4
> Python 2.4.2 (#1, Jan  6 2006, 12:06:26)
> [GCC 3.2.3] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> 
>  >>>>>> __requires__ = 'ipython==0.7.0'
>  >>>>>> import pkg_resources
>  >>>>>> pkg_resources.resource_string('ipython==0.7.0', 'ipython')
> 
> Traceback (most recent call last):
>    File "<stdin>", line 1, in ?
>    File
> "/home/travisc/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/pkg_resources.py",
> line 688, in resource_string
>      return get_provider(package_or_requirement).get_resource_string(
>    File
> "/home/travisc/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/pkg_resources.py",
> line 119, in get_provider
>      __import__(moduleOrReq)
> ImportError: No module named ipython==0.7.0
> 
>  >>>>>> pkg_resources.get_provider('ipython==0.7.0')
> 
> Traceback (most recent call last):
>    File "<stdin>", line 1, in ?
>    File
> "/home/travisc/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/pkg_resources.py",
> line 119, in get_provider
>      __import__(moduleOrReq)
> ImportError: No module named ipython==0.7.0

Neither of these functions take the same kind of argument that
pkg_resources.run_script() takes, so it's not surprising that what you wrote
doesn't work.

It's a bit difficult to diagnose without seeing your filesystem. Where are both
of the ipython eggs? Are they both in
/home/travisc/lib/python2.4/site-packages/? Is that a local site-packages for a
system Python executable, or is your Python executable ~/bin/python2.4, too?

-- 
Robert Kern
robert.kern at gmail.com

"In the fields of hell where the grass grows high
 Are the graves of dreams allowed to die."
  -- Richard Harter