Gael Varoquaux wrote:
>> The issue of configuration has come up several times on the mailing
>> lists over the last few years, and Fernando's tconfig feels like the
>> right solution. On the other hand, I can't be too enthusiastic about
>> pushing for inclusion in matplotlib in the near future, because I
>> havent been able to install traits as a separate package. At the
>> moment, the following command
>> easy_install -f
>> "enthought.traits < 3.0a"
>> does not install all the required modules. Running this command:
What didn't get installed that should have been? Definitely this
command line *should* have worked to get you a working install of
traits, even if it did install too many things.
That installed etsconfig, util, and traits. I can import traits, but when I
run John Hunters mpl1.py script, I get messages like:
Traceback (most recent call last):
File "mpl1.py", line 32, in <module>
File "mpl1.py", line 65, in Affine
data = traits.Array('d', (3,3))
line 329, in __call__
return self.maker_function( *args, **metadata )
line 805, in Array
return _Array( typecode, shape, value, coerce = False, **metadata )
line 877, in _Array
from enthought.traits.ui.api import ArrayEditor
line 69, in <module>
from tree_node \
line 36, in <module>
from enthought.resource.api \
ImportError: No module named resource.api
>> sudo easy_install -f
>> "enthought.etsconfig < 3.0a" "enthought.util <3.0a" "enthought.debug
>> will get you traits, along with debug, developer, envisage, etsconfig,
>> help io, logger, naming, plugins.python_shell, plugins.text_editor,
>> pyface, resource, sweet_pickle, traits.ui.wx, type_manager, and util.
>> Remember that email we got a while back from the guy complaining about
>> the ubuntu package manager installing too many gui toolkits? Hopefully
>> it is in Enthought's best interest to work out the dependency issues.
> Damn it. That certainly is not normal. I am CCing the enthought-dev
> mailing-list where somebody can take care of this.
Hmm, why did you choose to install enthought.debug?
It was suggested here:
The current source
for enthought.traits requires only enthought.etsconfig (which has no
other dependencies) and enthought.util (which, without extras, requires
I think the problem lies in traits.ui, which is looking for
enthought.resource, which requires pyface.
The list of dependencies you're seeing is because enthought.debug egg
does require enthought.pyface, which then heads up a big, big chain of
other dependencies. That's just the state of the code soon after
switching over from a monolithic distribution plan. We do hope to
further minimize the dependencies of enthought.pyface, and all of the
enthought components in the future!
I'm looking forward to working more with traits, so this is great news. I
think the same traits.ui issue may be preventing us from using traits3, since
enthought.resource does not exist in the trunk.
On Sunday 22 July 2007 12:12:40 pm Dave Peterson wrote:
> On Sun, Jul 22, 2007 at 11:43:31AM -0400, Darren Dale wrote: