On Mon, Jul 16, 2007 at 10:31:03PM -0500, John Hunter wrote:
On 7/16/07, Eric Firing [EMAIL PROTECTED] wrote:
Are any real, live projects outside of enthought making major use of
traits? Or would we be the first?
I am happy to be the first at this point -- enthought has done a lot
to
Gael Varoquaux wrote:
On Mon, Jul 16, 2007 at 10:31:03PM -0500, John Hunter wrote:
I am happy to be the first at this point -- enthought has done a lot
to support traits. Traits has one of the most impressive pieces of
technical documentation in the scientific python community.
I
On Tue, Jul 17, 2007 at 08:01:41AM -0400, Michael Droettboom wrote:
TraitsUI seems really cool, but there are a couple of reasons I think
that should probably be considered lower priority. For one, it would
need to be generalized and ported (backend-ed) for all of matplotlib's
many gui
On Tuesday 17 July 2007 08:01:41 am Michael Droettboom wrote:
Gael Varoquaux wrote:
On Mon, Jul 16, 2007 at 10:31:03PM -0500, John Hunter wrote:
I am happy to be the first at this point -- enthought has done a lot
to support traits. Traits has one of the most impressive pieces of
On Tuesday 17 July 2007 09:15:15 am Darren Dale wrote:
I'm really impressed with how readable and well organized the code is in
ipython1. It looks like their approach to configuration has been carefully
considered. Any chance we can follow their lead? It looks like it would be
a good fit: we
On Tuesday 17 July 2007 09:33:47 am John Hunter wrote:
We should also consider getting out a 0.91 release as soon as we can
finish the numpification, because Michael has done a lot of good work.
So much to do
I'd like to add the dict-based validation scheme for 0.91. It should be quick,
On Tue, Jul 17, 2007 at 08:33:47AM -0500, John Hunter wrote:
Speaking of branches, we may need to seriously consider a branch here,
mpl1. The changes here may involve breaking a fair amount of code,
which I don't mind doing to get it right, but I'm somewhat inclined to
branch off here for
On 7/17/07, Darren Dale [EMAIL PROTECTED] wrote:
I'd like to add the dict-based validation scheme for 0.91. It should be quick,
and then I can focus on traits and a new config scheme, in an mpl1 branch if
we decide that is best.
Sounds like a good plan.
This is exactly the sort of thing that I thought a transform approach
would make easier to do. So if it isn't urgent, waiting probably
would be better. (by the way, we see exactly the same sort of log
scale you propose in one of our older (non-python) packages. So there
is a call for this
Sorry for double posting. Apparently the original posting was html formatted,
and looked nonsensical. Hopefully this one is more clear:
On Tuesday 17 July 2007 02:31:02 pm Darren Dale wrote:
On Tuesday 17 July 2007 09:33:47 am John Hunter wrote:
Speaking of branches, we may need to seriously
On 7/17/07, Michael Droettboom [EMAIL PROTECTED] wrote:
TraitsUI seems really cool, but there are a couple of reasons I think
that should probably be considered lower priority. For one, it would
need to be generalized and ported (backend-ed) for all of matplotlib's
many gui backends. Also,
I have written a small script that uses pylab to retrieve the data for
the MPL colormaps. I am thinking of checking in both the script, and the
resulting data in Mayavi2 (FBSD licenced). Can I do such a thing
(stealing colormaps ?).
Cheers
Hi all,
this is an important discussion also for us (ipython), so I'll go in
some detail into things. It would be great if out of this we got
something that both ipython and matplotlib could reuse for the long
haul, though I'm not sure (in a sense, ipython has some nastier
requirements that mpl
13 matches
Mail list logo
