Re: chaco ets build - missing icons

On Tue, 2009-06-30 at 17:51 -0500, Dave Peterson wrote:
> > I've seen someone else report that setuptools does not have support
> > for SVN 1.6, so I believe this is the root of your problem.
> >   
> 
> Since I don't have an SVN 1.6 checkout, I can't tell for sure if
> the .svn data files are supported.  But Didrik should be able to do so
> by looking at the code in setuptools/command/sdist.py -- look at the
> code in entries_finder().  In the trunk:
> 
> http://svn.python.org/projects/sandbox/trunk/setuptools/setuptools/command/sdist.py
> it certainly only explicitly mentions svn 1.4 and 1.5.

I've downgraded the sliksvn client from 1.6 to 1.5.4. I'll keep you
informed tomorrow as I have to redo an "ets co" on the full ETS (all
the .svn directory are in 1.6 format ...) and it's quiet late here.

Thanks for the help

Didrik

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

Re: Tutorial topics for SciPy'09 Conference

Hi,

On Mon, Jun 1, 2009 at 10:20 PM, Fernando Perez<fperez.net@...> wrote:
> The time for the Scipy'09 conference is rapidly approaching, and we
> would like to both announce the plan for tutorials and solicit
> feedback from everyone on topics of interest.

rather than rehash much here, where it's not easy to paste a table,
I've posted a note with the poll results here:

http://fdoperez.blogspot.com/2009/06/scipy-advanced-tutorials-results.html

The short and plain-text-friendly version is the final topic ranking:

1	Advanced topics in matplotlib use
2	Advanced numpy
3	Designing scientific interfaces with Traits
4	Mayavi/TVTK
5	Cython
6	Symbolic computing with sympy
7	Statistics with Scipy
8	Using GPUs with PyCUDA
9	Testing strategies for scientific codes
10	Parallel computing in Python and mpi4py
11	Sparse Linear Algebra with Scipy
12	Structured and record arrays in numpy
13	Design patterns for efficient iterator-based scientific codes
14	Sage
15	The TimeSeries scikit
16	Hermes: high order Finite Element Methods

Re: chaco ets build - missing icons

On Wed, 2009-07-01 at 01:12 +0200, Didrik Pinte wrote:
> I've downgraded the sliksvn client from 1.6 to 1.5.4. I'll keep you
> informed tomorrow as I have to redo an "ets co" on the full ETS (all
> the .svn directory are in 1.6 format ...) and it's quiet late here.

Robert, you rock ! It works as expected with a 1.5 version of the svn
client after having removed the data_files from Chaco's setup.py.

Sorry for all the mess around that. Bryce, you probably had the same
issue as me ? The data_files patch can safely be removed.

Didrik

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

Re: Memory leaks in Kiva

Hi,

Thanks for the fix! It stopped the leaking in Kiva, but there seems to
be one more leak, as fill_free_list keeps allocating memory. I created
a new ticket for that
(https://svn.enthought.com/enthought/ticket/1826).

Best Regards,
Joonas Paalasmaa
Finsor Ltd

On Thu, Jun 18, 2009 at 2:40 AM, bryce hendrix<bhendrix@...> wrote:
> Okay, all the leaks I could find were fixed (including the 2 reported). The
> fixes are in the trunk and will be in the next release.
>
> Bryce
>
> bryce hendrix wrote:
>
> Thanks for the info, I am looking at it today. I'll let you know when
> its fixed.
>
> Bryce
>
>
> Joonas Paalasmaa wrote:
>
>
> Hi,
>

Re: AppTools Recorder test failure

On 07/01/09 01:03, David Martin wrote:
> Seems I got carried away in explaining the problem and forgot to ask my 
> question =). Can Prabhu or someone else familiar with this part of 
> AppTools take a look at this failure?

I'll take a look when I get the chance this weekend.

prabhu

viewport

Dear List,

I'm surprised to see that contrary to vtk, in tvtk,
the Renderer class doesn't have a SetViewport method.

Thus, how can I define a viewport for a renderer ?

This is useful as I need two display two images side by side
for stereo rendering (geowall system).

Cheers,

yves

--

-- 
                                                 (o o)
--------------------------------------------oOO--(_)--OOo-------
  Yves Revaz
  Laboratory of Astrophysics EPFL
  Observatoire de Sauverny     Tel : ++ 41 22 379 24 28
  51. Ch. des Maillettes       Fax : ++ 41 22 379 22 05
  1290 Sauverny             e-mail : Yves.Revaz@...
  SWITZERLAND                  Web : http://www.lunix.ch/revaz/
----------------------------------------------------------------

[trait] updating list without notifying...

Hi all,

When I want to update a trait without notifying it, I use

self.set(trait_change_notify=False,
         foo='bar')

How can I update a trait List (adding item for instance) without
notifying it?

I ask because

self.set(trait_change_notify=False,
         foo.append('bar'))

does not work.

TIA.

Cheers,

--

-- 
Fred

Re: extended names in Button Trait handlers

Luca Fasano <lucafasano <at> ...> writes:

> 
> Hi all,
> I noticed there's a method decorator  <at> on_trait_changed(*extended name*)
> which is very helpful if you want to handle children changes.
> 
> I need a similar method which handle only *button fired* events using
> *extended names* (for example
> " <at> on_button_fired('child.subchild.button1') " )
> What is the cleaner way to obtain this behaviour? Does it exist a
> decorator which handle *only* fired events? 
> 
> I could use  <at> on_trait_changed in this case too, but it handle not only
> fired events.
> 
> Thaks
> 

Thanks to Robert Kern,
colons are surely more useful than dots for me, but I need to handle only button
fired events, and not all its events.

Re: extended names in Button Trait handlers

On Wed, Jul 1, 2009 at 10:37, LF<lucafasano@...> wrote:
> Luca Fasano <lucafasano <at> ...> writes:
>
>>
>> Hi all,
>> I noticed there's a method decorator  <at> on_trait_changed(*extended name*)
>> which is very helpful if you want to handle children changes.
>>
>> I need a similar method which handle only *button fired* events using
>> *extended names* (for example
>> " <at> on_button_fired('child.subchild.button1') " )
>> What is the cleaner way to obtain this behaviour? Does it exist a
>> decorator which handle *only* fired events?
>>
>> I could use  <at> on_trait_changed in this case too, but it handle not only
>> fired events.
>>
>> Thaks
>
> Thanks to Robert Kern,
> colons are surely more useful than dots for me, but I need to handle only button
> fired events, and not all its events.

If you are listening to a Button() trait, that *is* the only event
that it will handle. Can you show me some code that displays the
undesired behavior? I'm not sure that I understand your problem now.

--

-- 
Robert Kern

Re: [trait] updating list without notifying...

On Wed, Jul 1, 2009 at 08:35, fred<fredmfp <at> gmail.com> wrote:
> Hi all,
>
> When I want to update a trait without notifying it, I use
>
> self.set(trait_change_notify=False,
>         foo='bar')
>
> How can I update a trait List (adding item for instance) without
> notifying it?
>
> I ask because
>
> self.set(trait_change_notify=False,
>         foo.append('bar'))
>
> does not work.

There isn't an official way, but a workaround would look like this:
from enthought.traits.api import HasTraits, List

class SilentAppender(HasTraits):
    foo = List()

    def silent_append(self, x):
        name_items = self.foo.name_items
        self.foo.name_items = None
        try:
            self.foo.append(x)
        finally: