Hi Robert,

This sort of thing really should be done on the enthought-dev mailing list so that the public at large can benefit should we find an answer for the problem.  As a result, I'm redirecting my reply there -- please do the same for any follow-ups.


robert somerville wrote:

re https://mail.enthought.com/pipermail/enthought-dev/2009-June/022256.html

hi I have tried everything in numerous combinations, mixing and trying all suggestions i find on ENT webpage .. I am running  python 2.6.2 on Ubuntu 9.04  ..

I still get "ImportError: No module named chaco.shell" no matter what i do

Help, can you give me some idea of where to go from here in detail (i was using the Ubuntu package manager a bit also ..) ????  is there a set of commands that will allow me to recover back to a base setup , in order to start over ???

I'm not a very experienced Ubuntu dpkg/apt-get user so I'm not quite sure of the following, but what I would do first is to try and determine where the chaco you *are* getting is on the disc.   This can be done by:
    python -c "from enthought import chaco; print chaco"
at a terminal window.  Once you know where that Chaco is, you can go about trying to fix the problem but the solution will depend on what you find out.

That being said, the command to remove something installed via apt-get is as follows, assuming Chaco was installed via apt-get:
    sudo apt-get remove python-enthought-chaco

Unfortunately, there is no corresponding command for an install done via easy_install.   Instead you have to find the location the install was done to and then manually remove the relevant  Chaco egg directory or file.

Hope that's enough to get you started!


-- Dave

can you please help this newbie Enthought / python programmer and tell me what i have done wrong in installation or environment ...

hi ; i am trying the example program in tutorial 1:
http://code.enthought.com/projects/chaco/docs/html/user_manual/tutorial_1.html#tutorial-1
>from numpy import *
>from enthought.chaco.shell import *
>
>x = linspace(-2*pi, 2*pi, 100)
>y = sin(x)
>
>plot(x, y, "r-")
>title("First plot")
>ytitle("sin(x)")
>show()

run as is , i get:

>[bob <at> oberon /home/robert/python]: python test1a.py
>Traceback (most recent call last):
> File "test1a.py", line 2, in <module>
> from enthought.chaco.shell import *

>ImportError: No module named chaco.shell

if I hack it, i can get this fragment to work:

>from numpy import *
>from enthought.traits.api import HasTraits, Instance
>from enthought.chaco.shell import *
>x = linspace(-2*pi, 2*pi, 100)
>y = sin(x)
>plot(x, y, "r-")
>title("First plot")
>ytitle("sin(x)")
>show()

concerning your previous suggestions, here is the output i get :
[bob <at> oberon /home/robert/python]: python -c "from enthought import chaco; print chaco"
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: cannot import name chaco


[bob <at> oberon /home/robert/python]: python -c "import enthought; print enthought"
<module 'enthought' (built-in)>

On Mon, Nov 30, 2009 at 3:38 PM, Dave Peterson <dpeterson <at> enthought.com> wrote:

Hi Robert,

This sort of thing really should be done on the enthought-dev mailing list so that the public at large can benefit should we find an answer for the problem.  As a result, I'm redirecting my reply there -- please do the same for any follow-ups.


robert somerville wrote:

re https://mail.enthought.com/pipermail/enthought-dev/2009-June/022256.html

hi I have tried everything in numerous combinations, mixing and trying all suggestions i find on ENT webpage .. I am running  python 2.6.2 on Ubuntu 9.04  ..

I still get "ImportError: No module named chaco.shell" no matter what i do

Help, can you give me some idea of where to go from here in detail (i was using the Ubuntu package manager a bit also ..) ????  is there a set of commands that will allow me to recover back to a base setup , in order to start over ???

I'm not a very experienced Ubuntu dpkg/apt-get user so I'm not quite sure of the following, but what I would do first is to try and determine where the chaco you *are* getting is on the disc.   This can be done by:
    python -c "from enthought import chaco; print chaco"
at a terminal window.  Once you know where that Chaco is, you can go about trying to fix the problem but the solution will depend on what you find out.

That being said, the command to remove something installed via apt-get is as follows, assuming Chaco was installed via apt-get:
    sudo apt-get remove python-enthought-chaco

Unfortunately, there is no corresponding command for an install done via easy_install.   Instead you have to find the location the install was done to and then manually remove the relevant  Chaco egg directory or file.

Hope that's enough to get you started!


-- Dave

Hi Robert,

I'm real sorry you're having such difficulty!  However, I can assure you that a good number of people have been able to install ETS, so it can definitely be done. 

I suspect that you are either (a) missing something fundamental with your Python install or (b) having side effects from mixing different install methods which is likely a result of not cleaning up one completely before trying the next.  Either of these are quite likely for a newbie Python programmer.

I'd like to help you get going with ETS but the information below doesn't really give me to many areas to offer anything because it's pretty non-specific.  However, I do have some comments made inline below.

-- Dave

robert somerville wrote:

after trying every possible combination of installation instructions on the Enthought website, i find that the bugs just move around .. obviously there are various code incompatabilities ...

Actually, there are installation incompatibilities as a result of a proliferation of install methods, tools, and the Python features (mostly namespace packages) used in ETS.  You need to pick a method that fits with your goals and then stick to it.

what i need is VERY well documented way to install ETS and clearly explained methods of debugging the installations .... what i published below no longer holds, but it appears that my problems are much worse now ... I'm tempted to give up and wait till i can find somebody (in person) that can explain this system(ETS) installation in detail ...

There is no way we can publish instructions on how to debug every possible installation issue, that's just too wide a space to cover.   What we can do is respond to requests for help, which I'm still doing.  Unfortunately, my help isn't very useful if you keep changing things around before we can suggest next steps.    I understand you want to get it working ASAP, so I understand your desire to keep trying things.  Just realize it means I can't keep up on offering install debugging help.

Newbie temporarily gives up .....

On Mon, Nov 30, 2009 at 7:16 PM, robert somerville <rbrt.somerville-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

can you please help this newbie Enthought / python programmer and tell me what i have done wrong in installation or environment ...

hi ; i am trying the example program in tutorial 1:
http://code.enthought.com/projects/chaco/docs/html/user_manual/tutorial_1.html#tutorial-1
>from numpy import * >from enthought.chaco.shell import * > >x = linspace(-2*pi, 2*pi, 100) >y = sin(x) > >plot(x, y, "r-") >title("First plot") >ytitle("sin(x)") >show() run as is , i get: >[bob <at> oberon /home/robert/python]: python test1a.py >Traceback (most recent call last): > File "test1a.py", line 2, in <module> > from enthought.chaco.shell import *

>ImportError: No module named chaco.shell

if I hack it, i can get this fragment to work: >from numpy import * >from enthought.traits.api import HasTraits, Instance >from enthought.chaco.shell import * >x = linspace(-2*pi, 2*pi, 100) >y = sin(x) >plot(x, y, "r-") >title("First plot") >ytitle("sin(x)") >show()

This is very weird that inserting an import of enthought.traits.api causes the import of enthought.chaco.shell to work.  I'm at a loss to explain what is going on there, but more data may help.  Given that you said you've tried other things since this, I'm not sure we can figure this out, but I would have asked you to tell me where the enthought.traits.api was installed at by sending the output of:
    python -c "from enthought.traits import api; print api:"

concerning your previous suggestions, here is the output i get : [bob <at> oberon /home/robert/python]: python -c "from enthought import chaco; print chaco" Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: cannot import name chaco [bob <at> oberon /home/robert/python]: python -c "import enthought; print enthought" <module 'enthought' (built-in)>

The "enthought" package should not be a built-in module.  I'm at a loss to explain why your Python thinks it is, but if I had to guess, I'd say that you mistakenly created or install into your /home/robert/python/lib/python2.6 directory rather than /home/robert/python/lib/python2.6/site-packages directory.

On Mon, Nov 30, 2009 at 3:38 PM, Dave Peterson <dpeterson-SCgzsaguwNrby3iVrkZq2A@public.gmane.org> wrote:

Hi Robert,

This sort of thing really should be done on the enthought-dev mailing list so that the public at large can benefit should we find an answer for the problem.  As a result, I'm redirecting my reply there -- please do the same for any follow-ups.


robert somerville wrote:

re https://mail.enthought.com/pipermail/enthought-dev/2009-June/022256.html

hi I have tried everything in numerous combinations, mixing and trying all suggestions i find on ENT webpage .. I am running  python 2.6.2 on Ubuntu 9.04  ..

I still get "ImportError: No module named chaco.shell" no matter what i do

Help, can you give me some idea of where to go from here in detail (i was using the Ubuntu package manager a bit also ..) ????  is there a set of commands that will allow me to recover back to a base setup , in order to start over ???

I'm not a very experienced Ubuntu dpkg/apt-get user so I'm not quite sure of the following, but what I would do first is to try and determine where the chaco you *are* getting is on the disc.   This can be done by:
    python -c "from enthought import chaco; print chaco"
at a terminal window.  Once you know where that Chaco is, you can go about trying to fix the problem but the solution will depend on what you find out.

That being said, the command to remove something installed via apt-get is as follows, assuming Chaco was installed via apt-get:
    sudo apt-get remove python-enthought-chaco

Unfortunately, there is no corresponding command for an install done via easy_install.   Instead you have to find the location the install was done to and then manually remove the relevant  Chaco egg directory or file.

Hope that's enough to get you started!


-- Dave

_______________________________________________ Enthought-Dev mailing list Enthought-Dev-SCgzsaguwNrby3iVrkZq2A@public.gmane.org https://mail.enthought.com/mailman/listinfo/enthought-dev

_______________________________________________
Enthought-Dev mailing list
Enthought-Dev-SCgzsaguwNrby3iVrkZq2A@public.gmane.org
https://mail.enthought.com/mailman/listinfo/enthought-dev

On Dec 1, 2009, at 11:21 AM, Dave Peterson wrote:
>> [bob <at> oberon /home/robert/python]: python -c "import enthought;
>> print enthought"
>> <module 'enthought' (built-in)>
> The "enthought" package should not be a built-in module.  I'm at a
> loss to explain why your Python thinks it is, but if I had to guess,
> I'd say that you mistakenly created or install into your /home/
> robert/python/lib/python2.6 directory rather than /home/robert/
> python/lib/python2.6/site-packages directory.

This strikes me as extremely odd.  There's no way the enthought
namespace should appear as a built-in.  But, to echo your sentiments
Dave, there is not much that we can do to help unless we are given
detailed information about the steps that Robert took, and perhaps an
overview of how things are set up on his machine now.  At a minimum:

- the location of the python interpreter, and the contents of his site-
packages
- if setuptools is installed, the contents of site-packages/easy-
install.pth
- the value of the PYTHONPATH environment variable, if it is defined
- the location where he has "installed" or attempted to install ETS
- where he has been trying to run the demos and examples (e.g. does
his working directory have a subdir named 'enthought' with an
__init__.py in it?)

That would at least be a useful start.

-Peter

_______________________________________________
Enthought-Dev mailing list
Enthought-Dev-SCgzsaguwNrby3iVrkZq2A@public.gmane.org
https://mail.enthought.com/mailman/listinfo/enthought-dev

On Tue, Dec 01, 2009 at 10:49:21AM -0700, robert somerville wrote:
>    here is the current state of my system:

OK, looking the information you provided, you indeed have a mess due to
different install mechanisms. Now before reviewing this and explaining,
let me give my view on the situation. The reason these problem arise is
that there are many ways of installing software on a computer. Not only
are there constraints to satisfy from the system administration point of
view (isolation of system libraries versus user libraries), but also
different requirements (such as priority on system consistency, versus
priority on flexibility) have lead to different choices made by different
distribution mechanisms (Linux distributions, setuptools, vanilla
Python). This is fairly unfortunate, and is a technico-social problem
that arises quite often when many developers try to tackle a hard problem
with limited resources. In our case, I believe that the problem extends
way further than the ETS in all the Python world. Deploying any complex
application in Python nowadays is not perfectly robust. To end this
paragraph on a positive point, I also believe that the situation will
improve in the next few years. First of all, there is a set of
best-practices that are slowly being established. Second, relative imports
by default will make import-namespace polution harder. Last the people in
charge of the distribution tools in Python have started a very healthy
discussion about the problems.

Now, in the mean time, we need to solve problem by hand, for lack of a
magic bullet.

>    python -c "from enthought.traits import api; print api"
>    <module 'enthought.traits.api' from
>    '/usr/lib/python2.6/dist-packages/enthought/traits/api.pyc'>

If I am not wrong, that tells us that you have a Traits install that does
not use namespace packages. I believe that you will need to clean up this
install, as it cannot work with namespace package installs, which is the
privileged way of installing ETS. How did you install it? If you install
traits and Enthought tools via your distribution packages, simply remove
them with the package management system.

>    test1.py
>    from numpy import *
>    from enthought.chaco.shell import *

>    [bob <at> oberon /home/robert/python]: python test1a.py
>    Traceback (most recent call last):
>    ? File "test1a.py", line 2, in <module>
>    ??? from enthought.chaco.shell import *
>    ImportError: No module named chaco.shell

>    test1a.py
>    from numpy import *

>    from enthought.traits.api import HasTraits, Instance
>    #from enthought.chaco.api import Plot, ArrayPlotData
>    from enthought.chaco.shell import *

>    [bob <at> oberon /home/robert/python]: python test1.py
>    Traceback (most recent call last):
>    ? File "test1.py", line 5, in <module>
>    ??? from enthought.chaco.shell import *
>    ? File
>    "/usr/local/lib/python2.6/dist-packages/Chaco-3.2.1.dev_r24978-py2.6-linux-x86_64.egg/enthought/chaco/shell/__init__.py",
>    line 2, in <module>
>    ??? from commands import *
>    ? File
>    "/usr/local/lib/python2.6/dist-packages/Chaco-3.2.1.dev_r24978-py2.6-linux-x86_64.egg/enthought/chaco/shell/commands.py",
>    line 3, in <module>
>    ??? import wx
>    ? File
>    "/usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode/wx/__init__.py",
>    line 45, in <module>
>    ??? from wx._core import *
>    ? File "/usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode/wx/_core.py",
>    line 4, in <module>
>    ??? import _core_
>    ImportError:
>    /usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode/wx/_core_.so: symbol
>    _ZN12wxSizerFlags24ReserveSpaceEvenIfHiddenEv, version WXU_2.8.8 not
>    defined in file libwx_gtk2u_core-2.8.so.0 with link time reference
>    [bo

We can learn two things from the above:

* We can see from the above that you have eggs installed (the path
 references a specialy-named folder '*.egg'). This is incompatible with
 the non-egg install of Traits. This is why I am suggesting to remove
 the Traits install in /usr.

* You have a version of gtk that binary-incompatible with something other
 library loaded (I am not sure which one). I would suspect that the
 version of Chaco that you have was not compiled on this system. How did
 you install Chaco? Can you try removing it and reinstalling it, if you
 know how to do the build?

I am sorry that you are struggling. Trust me, none of us enjoy the
situation.

Hope this helps,

Gaël

_______________________________________________
Enthought-Dev mailing list
Enthought-Dev-SCgzsaguwNrby3iVrkZq2A@public.gmane.org
https://mail.enthought.com/mailman/listinfo/enthought-dev