John,
You are going great guns with mpl1; I am trying to get spun up on
traits, and to understand where you are going with mpl1. In general I
like what I see--as expected. Regarding the following comments: I
recognize that you are engaged in a sketching activity, and I may be
thinking premat
On Sat, Jul 21, 2007 at 10:41:27PM -1000, Eric Firing wrote:
> You raised the question of 3D. I don't know anything about fancy 3D
> with hardware acceleration etc., but for the simplest 3D it seems like
> everything can be done at the model stage of the transformation;
> everything after that
>> Im attaching a patch
> Is the patch against current SVN?
It was one version out of date. Here is a new one, against 2533
Index: mpltest.py
===
--- mpltest.py (revision 2533)
+++ mpltest.py (working copy)
@@ -5,43 +5,14 @@
import
On 7/22/07, Eric Firing <[EMAIL PROTECTED]> wrote:
> You are going great guns with mpl1; I am trying to get spun up on
> traits, and to understand where you are going with mpl1. In general I
> like what I see--as expected. Regarding the following comments: I
> recognize that you are engaged in a
On 7/21/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> Im attaching a patch, it includes lots of changes to mplconfig.py, a realistic
> mplrc.conf file (feel free to rename it to mpl.conf or matplotlib.conf or
> whatever seems standard), and a backup of that .conf file. The mpltest lets
> me try you
Hi John,
On Sunday 22 July 2007 9:51:05 am John Hunter wrote:
> On 7/21/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> > 2) It would be nice to be able to write a default file that has
> > everything commented out with the exception of backend.use and numerix.
> > We comment out all the parameters i
On Sun, Jul 22, 2007 at 11:43:31AM -0400, Darren Dale 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
On 7/22/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> 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
Well, we always have matplotli
On 7/22/07, Dave Peterson <[EMAIL PROTECTED]> wrote:
> Hmm, why did you choose to install enthought.debug? The current source
> for enthought.traits requires only enthought.etsconfig (which has no
> other dependencies) and enthought.util (which, without extras, requires
> only enthought.traits.)
On Sunday 22 July 2007 12:12:40 pm Dave Peterson wrote:
> Gael Varoquaux wrote:
> > On Sun, Jul 22, 2007 at 11:43:31AM -0400, Darren Dale 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
> >> ri
On Sunday 22 July 2007 1:04:10 pm Darren Dale wrote:
> I think the problem lies in traits.ui, which is looking for
> enthought.resource, which requires pyface.
Scratch that. I thought I remembered that pyface was getting pulled in by
enthought.resource, but I think that was wrong. Somewhere along
On Sunday 22 July 2007 12:46:50 pm John Hunter wrote:
> The following, however, gives me a broken install:
>
> sudo rm -rf /usr/local/lib/python2.5/site-packages/enthought*
> sudo easy_install -f
> http://code.enthought.com/enstaller/eggs/source/unstable
> "enthought.traits < 3.0a"
>
> eg, with
John Hunter wrote:
> On 7/22/07, Dave Peterson <[EMAIL PROTECTED]> wrote:
>
>> Hmm, why did you choose to install enthought.debug? The current source
>> for enthought.traits requires only enthought.etsconfig (which has no
>> other dependencies) and enthought.util (which, without extras, require
Dave Peterson wrote:
> It does look like one of the dependencies in enthought.traits is wrong
> then. In particular, it was thought that enthought.resource was only
> required if you actually *used* Traits UI features. I just looked at
> the code and the only import, in traits, of a package f
On 7/22/07, Dave Peterson <[EMAIL PROTECTED]> wrote:
> Just uploaded a new source tarball that I believe should have this fixed
> so that you don't need to install enthought.resource. Basically, I
Bingo, I am now getting a working install with
sudo easy_install -f
http://code.enthought.com/enst
15 matches
Mail list logo
