Ateljevich, Eli | 1 Mar 01:00
Picon
Favicon
Gravatar

Re: chaco.shell status

> > 3. I need a "session manager" for envisage as well as scripting. The
> > main difference is the source of the window/frame. Could that be
> > configured to be swappable somehow?
> 
> Can you elaborate?  Are you referring to replacing the PlotSession
> with something that is duck-type compatible but knows about
> Envisage?  If so, this is also quite easy: at the top of commands.py,
> the global PlotSession object is created.  We can add a function to
> replace that with a different, external session object.  Also, we
> should factor out the interface for PlotSession into an abstract
class.

Yes. This is what I am asking for. It is easier for me to achieve the
type of script-gui interchangeability I am shooting for if that
interface were exposed.

 
> I agree that these would be nice features to have.  It would be very
> sweet to have a general sync() function:
>     sync(plot1, "x_range", plot2, "y_range")
Yup. That is the stuff.

> If you are not familiar
> with the Plot and PlotData stuff, take a look in chaco2/examples/
> basic; the examples in there are using Plot instead of the
> create_line_plot() and create_scatter_plot() functions in
> plot_factory.py.  I hope to be able to deprecate plot_factory at some
> point...
I think the deprecation is fine. I'd like to clarify something about
Plot and PlotData, though. It seems that PlotData assume a common index.
(Continue reading)

Bill Baxter | 1 Mar 01:09
Picon
Gravatar

Re: enstaller now installs scripts to the Scripts dir

The enstaller-latest-py2.4.egg link seems to be missing.
So run_enstaller currently fails:
Installing http://code.enthought.com/enstaller/eggs/enstaller-latest-py2.4.egg
to temp location
Traceback (most recent call last):
  File "run_enstaller.py", line 128, in ?
    run_enstaller( args )
  File "run_enstaller.py", line 82, in run_enstaller
    egg = download_enstaller( repo=REPO, version=VERSION, to_dir=tmpdir )
  File "run_enstaller.py", line 51, in download_enstaller
    src = urllib2.urlopen( url )
  File "C:\python24\lib\urllib2.py", line 130, in urlopen
    return _opener.open(url, data)
  File "C:\python24\lib\urllib2.py", line 364, in open
    response = meth(req, response)
  File "C:\python24\lib\urllib2.py", line 471, in http_response
    response = self.parent.error(
  File "C:\python24\lib\urllib2.py", line 402, in error
    return self._call_chain(*args)
  File "C:\python24\lib\urllib2.py", line 337, in _call_chain
    result = func(*args)
  File "C:\python24\lib\urllib2.py", line 480, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 404: Not Found

--bb

On 3/1/07, Bryce Hendrix <bhendrix@...> wrote:
> One of the most common complaints with eggs installed by enstaller is
> that the scripts were put in the wrong place (most commonly the
(Continue reading)

Peter Wang | 1 Mar 01:28

Re: chaco.shell status

On Feb 28, 2007, at 6:00 PM, Ateljevich, Eli wrote:

> I think the deprecation is fine. I'd like to clarify something about
> Plot and PlotData, though. It seems that PlotData assume a common  
> index.

Nope, not at all.  I tried to make PlotData be an almost trivial  
interface so that it can interface easily with any application-side  
model.

> My apps have data that "belong together" but don't share an index.  
> They
> would look perfectly natural plotted together on the same axes --  
> and in
> some cases (e.g. viewing the output of a decimation) that might be the
> goal of the plot. In the design, is this envisioned as two Plots?

Maybe.  Plot can support multiple plots with different indices:

p = Plot(pd)
p.plot(("x1", "y1"))
p.plot(("x2", "y2"))

They will be added to the same range.  Now, in the case of  
decimation, the x1 might have 100000 points and x2 might only have  
100, but as long as the actual x-values are numerically compatible,  
then you can put them on the same, single Plot object.

It's only when you need to overlay two plots with different data  
space views that you will need to create two Plot objects, since  
(Continue reading)

David C. Morrill | 1 Mar 02:04

Re: Traits and XML input/output

Brennan Williams wrote:

> It sounds like their isn't anything closely tied in with traits? correct?
>  It sort of seems strange that all the work is done with traitsui and it 
> makes me wonder if there
> could be a sort of traitsxml?
>   
Traits UI is a collection of Python object classes that are used to 
create user interfaces for traits-based applications. It is not used to 
completely describe the content of traits objects, but only those 
aspects that pertain to the UI. It also contains other information that 
does not directly relate to the objects, but instead relates to the 
implementation of the UI for those objects.

Now it would be possible to define an XML schema for defining a traits 
UI, but that would be different than a schema to represent an arbitrary 
hierarchy of traits-based objects.

It seems to me that an XML schema for representing an arbitrary 
traits-based object hierarchy would not be substantially different than 
one for arbitrary Python objects. So it's not really a traits question 
so much as it is a Python XML serialization question, which I'm sure has 
already been addressed in several different ways by other Python tools 
and packages...

Dave Morrill
Peter Wang | 1 Mar 05:20

Re: chaco.shell status

On Feb 28, 2007, at 6:28 PM, Peter Wang wrote:

> If you wanted to merge two Plot's list of renderers together into a
> single legend... there's no facility in the legend itself to cleanly
> handle a list of dictionaries. ... This
> is somewhat ugly and I will mull over the best way to support
> multiple dicts in the Legend.

I'm being retarded.  I'll just change the legend to accept any  
general iterable, and it will try to do the Right Thing  (e.g. split  
up tuples into (name, renderer) pairs, or get key:value out of a  
dict, etc.)

Now, there's no generic traits adapter that will merge two lists into  
one, but you can listen for the "plots_items" on both Plot instances  
and update the legend's dictionary appropriately by just adding  
plots.items() from both.

-Peter
Fernando Perez | 1 Mar 06:15
Picon
Gravatar

Re: [SciPy-user] Any Books on SciPy?

On 2/28/07, Gael Varoquaux <gael.varoquaux@...> wrote:
> On Wed, Feb 28, 2007 at 01:22:34AM -0700, Fernando Perez wrote:
> > > As you are probably aware (I think you follow the enthought-dev ML)
> > > Prabhu and I are currently trying to find time to code a nice "mlab"
> > > interface to mayavi2. Once it has made some progress (expect two to three
> > > months) it will be much nicer than the current way of using mayavi from
> > > python. Of course there is the problem that mayavi2 is not properly
> > > distributed currently. That might change as enthought is currently
> > > pushing for a modular eggs-based version of their tool suite.
>
> > I know, I've been quietly following that discussion with the utmost
> > interest.  I'm hoping it will be ready by Saturday, b/c I'm having a
> > mini-sprint at my house with some students to port some old CFD code
> > to the new mayavi.  So you have 3 days to finish it :)
>
> Well well. Currently the API is not stable at all, and I do not want to
> freeze it (cf my last about this on the enthougt-dev ML). I can let this
> project steel even more sleep from me than my work already does, and move
> a bit forward to try and establish something that is closer to the API
> that I am aiming to, but even if I a manage to get something out (and when I
> am to tired I am not terribly productive), I need Prabhu to review it.
>
> All I can say is that mayavi.tools.mlab is not currently in its final
> form and I do not suggest using it, unless you are planning to modify the
> code you are writing. From the user point of view following the API
> change should not be a huge amount of work.
>
> The changes I would like do to the API are exposed in the mails:
> https://mail.enthought.com/pipermail/enthought-dev/2007-February/004425.html
> [[Enthought-dev] Mlab API, and usability]
(Continue reading)

bryce hendrix | 1 Mar 06:48

Re: enstaller now installs scripts to the Scripts dir

The "latest" version was used previously, but we're now able to always install the latest (and can even update itself). You'll need to download the new run_enstaller script, which you can find a link to at http://code.enthought.com/enstaller (at the bottom). Sorry for any confusion.

Bryce

Bill Baxter wrote:
The enstaller-latest-py2.4.egg link seems to be missing. So run_enstaller currently fails: Installing http://code.enthought.com/enstaller/eggs/enstaller-latest-py2.4.egg to temp location Traceback (most recent call last): File "run_enstaller.py", line 128, in ? run_enstaller( args ) File "run_enstaller.py", line 82, in run_enstaller egg = download_enstaller( repo=REPO, version=VERSION, to_dir=tmpdir ) File "run_enstaller.py", line 51, in download_enstaller src = urllib2.urlopen( url ) File "C:\python24\lib\urllib2.py", line 130, in urlopen return _opener.open(url, data) File "C:\python24\lib\urllib2.py", line 364, in open response = meth(req, response) File "C:\python24\lib\urllib2.py", line 471, in http_response response = self.parent.error( File "C:\python24\lib\urllib2.py", line 402, in error return self._call_chain(*args) File "C:\python24\lib\urllib2.py", line 337, in _call_chain result = func(*args) File "C:\python24\lib\urllib2.py", line 480, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) urllib2.HTTPError: HTTP Error 404: Not Found --bb On 3/1/07, Bryce Hendrix <bhendrix-SCgzsaguwNrby3iVrkZq2A@public.gmane.org> wrote:
One of the most common complaints with eggs installed by enstaller is that the scripts were put in the wrong place (most commonly the site-package dir). This is now fixed with the latest enstaller. Next time the enstaller egg is updated you should get the new and improved version. There are two ways to update your enstaller egg: 1) use setuptools 2) delete the enstaller egg from the site-packages dir and run 'run_enstaller' again (via start menu or \Python24\Tools\Scripts\run_enstaller.py) Bryce _______________________________________________ Enthought-dev mailing list Enthought-dev-oRDGkvazHdacsI7C1d+pp9BPR1lH4CV8@public.gmane.org https://mail.enthought.com/mailman/listinfo/enthought-dev
_______________________________________________ Enthought-dev mailing list Enthought-dev-oRDGkvazHdacsI7C1d+pp9BPR1lH4CV8@public.gmane.org https://mail.enthought.com/mailman/listinfo/enthought-dev

_______________________________________________
Enthought-dev mailing list
Enthought-dev@...
https://mail.enthought.com/mailman/listinfo/enthought-dev
Gael Varoquaux | 1 Mar 08:14
Favicon
Gravatar

Re: [SciPy-user] Any Books on SciPy?

On Wed, Feb 28, 2007 at 10:15:07PM -0700, Fernando Perez wrote:
> Unfortunately I haven't had enough mental bandwidth to pay enough
> attention to the details to give you any meaningful feedback.  But as
> we begin using it, don't worry: you'll hear me complain :)

Well the problem is that I have neither the free mental bandwidth to
think it over carefuly, nor enough uptime to implement it in time to hear
you complain. But time will tell...

Cheers,

Gaƫl
Picon

Problems installing in Mac os X recent svn

Hi all, I had a working installation of the Enthought tools (complete
svn download) running on my Mac 10.4.8 with the latest version of
xCode and current versions of numpy and scipy. It was working fine but
yesterday I decided to update and did an svn up, rebuild and now it
doesn't working.

I run:

python setup.py build_src build_clib build_ext --inplace

This changed in the wiki, any reason for not using build_inplace.sh?

Then, during the build it complains about the distribution option:

/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/distutils/dist.py:236:
UserWarning: Unknown distribution option: 'zip_safe'

Should it use scipy_distutils? or this has nothing to do with that?

Then during the initial stages of the build it complains with:

could not resolve pattern in 'chaco': 'demo/*.png'
non-existing path in 'chaco2': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'chaco2/contour': 'tests'
non-existing path in '.': 'charm/apps'
non-existing path in 'component': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'developer': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'debug': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'debug': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'enable2': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'endo': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'envisage': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'ets': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'gotcha': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'greenlet': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'guitest': '/Users/andres2/enthought/src/lib/__init__.py'
...
non-existing path in 'help': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'interpolate':
'/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'io': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'kiva': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'kiva': 'pil_fonts'
...
non-existing path in 'logger': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'mathematics':
'/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'mayavi': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'model': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'naming': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'persistence':
'/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'plugins': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'pyface': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'pyface': '/Users/andres2/enthought/src/lib/version.py'
non-existing path in 'pyface/tvtk':
'/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'pyface/tvtk': '/Users/andres2/enthought/src/__init__.py'
non-existing path in 'python': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'resource': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'resource_type':
'/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in '.': 'resource_type/images'
non-existing path in 'sharing': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in '.': 'sharing/test'
non-existing path in 'sweet_pickle':
'/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'testing': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'traits': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'traits/ui': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'traits/ui': '/Users/andres2/enthought/src/__init__.py'
non-existing path in 'traits/ui/wx': '/Users/andres2/enthought/__init__.py'
non-existing path in 'traits/ui/wx': '/Users/andres2/enthought/__init__.py'
non-existing path in 'traits/ui/wx': '/Users/andres2/enthought/__init__.py'
non-existing path in 'tvtk': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'type_manager':
'/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'units': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'util': '/Users/andres2/enthought/src/lib/__init__.py'
non-existing path in 'util': 'test'

The file [ENTHOUGHT]/src/lib/__init__.py does not exist, there is a
[ENTHOUGHT]/src/lib/enthought/__init__.py. I checked my backups and
this file was not there in my running version either.

Finally after the build is completed and I try to run mayavi2 I get this:

Traceback (most recent call last):
  File "./mayavi2", line 3, in ?
    from enthought.mayavi.scripts import mayavi2
  File "/Users/andres2/enthought/src/lib/enthought/__init__.py", line 26, in ?
    __import__('pkg_resources').declare_namespace(__name__)
ImportError: No module named pkg_resources

My installation of the different components seems to be working fine
and as I mentioned above an older svn version used to work just fine.
I appreciate any help you can provide.

Thanks,

Andres

--

-- 
Andres Gonzalez-Mancera
Biofluid Mechanics Lab
Department of Mechanical Engineering
University of Maryland, Baltimore County
andres.gonzalez@...
410-455-3347
Ateljevich, Eli | 1 Mar 22:04
Picon
Favicon
Gravatar

Re: chaco.shell status

> -----Original Message-----
> From: enthought-dev-bounces@... [mailto:enthought-dev-
> bounces@...] On Behalf Of Peter Wang
> Sent: Wednesday, February 28, 2007 4:28 PM
> To: enthought-dev@...
> Subject: Re: [Enthought-dev] chaco.shell status
> 
> Maybe.  Plot can support multiple plots with different indices:
> 
> p = Plot(pd)
> p.plot(("x1", "y1"))
> p.plot(("x2", "y2"))
> 
> They will be added to the same range

Gotcha. Well, I should have looked more carefully at Plot. I didn't
notice that a Plot is a collection of individual plotting items like
LinePlots each of which has a PlotData. I guess I expected Plot to be a
base of LinePlot based on the names (a misunderstanding you might want
to consider).

Now that this is clear:
1. Does a Plot know what to do when a PlotData is dropped on it? If so:
   a. Are there hooks to listen for that and tell when a subplot is
added? 
   b. Where would I register the adapter between my class(a TimeSeries)
and PlotData so that this capability would come to life.

2. If I wanted to create actions such as "Delete Current Plot" or
"Remove Item From Plot" I need to be able to select Plot areas on a
Figure and also a subplot on a Plot. How would you recommend I do that?
A graphical/ interactive solution would be great.

Appreciate your helping me with this -- I love all this new stuff you
are rolling out.

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

Gmane