Michele Mattioni | 3 Jan 10:41 2010
Picon

Installing mayavi bleeding edge

I followed the instruction[1] to install the svn mayavi with all the dependences, however I can install Mayavi properly.

This is the error:

    mattions <at> triton:Mayavi_3.3.1$ sudo ets develop
    [sudo] password for mattions:
    Running "/usr/bin/python setup.py develop --no-deps" within dir "/home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/Traits_3.2.1"
    running develop
    unrecognized .svn/entries format; skipping .
    running egg_info
    writing requirements to Traits.egg-info/requires.txt
    writing Traits.egg-info/PKG-INFO
    writing namespace_packages to Traits.egg-info/namespace_packages.txt
    writing top-level names to Traits.egg-info/top_level.txt
    writing dependency_links to Traits.egg-info/dependency_links.txt
    unrecognized .svn/entries format in
    reading manifest file 'Traits.egg-info/SOURCES.txt'
    writing manifest file 'Traits.egg-info/SOURCES.txt'
    running build_ext
    copying build/lib.linux-i686-2.6/enthought/traits/ctraits.so -> enthought/traits
    copying build/lib.linux-i686-2.6/enthought/traits/protocols/_speedups.so -> enthought/traits/protocols
    Creating /usr/local/lib/python2.6/dist-packages/Traits.egg-link (link to .)
    Traits 3.2.1.dev-r0 is already the active version in easy-install.pth

    Installed /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/Traits_3.2.1
    running build_docs
    Using source directory /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/Traits_3.2.1/docs/source
    Running Sphinx v0.6.2
    loading pickled environment... done
    building [html]: targets for 0 source files that are out of date
    updating environment: 0 added, 0 changed, 0 removed
    looking for now-outdated files... none found
    no targets are out of date.
    Running "/usr/bin/python setup.py develop --no-deps" within dir "/home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/TraitsGUI_3.1.1"
    running develop
    unrecognized .svn/entries format; skipping .
    running egg_info
    writing requirements to TraitsGUI.egg-info/requires.txt
    writing TraitsGUI.egg-info/PKG-INFO
    writing namespace_packages to TraitsGUI.egg-info/namespace_packages.txt
    writing top-level names to TraitsGUI.egg-info/top_level.txt
    writing dependency_links to TraitsGUI.egg-info/dependency_links.txt
    unrecognized .svn/entries format in
    reading manifest file 'TraitsGUI.egg-info/SOURCES.txt'
    writing manifest file 'TraitsGUI.egg-info/SOURCES.txt'
    running build_ext
    Creating /usr/local/lib/python2.6/dist-packages/TraitsGUI.egg-link (link to .)
    TraitsGUI 3.1.1.dev-r0 is already the active version in easy-install.pth

    Installed /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/TraitsGUI_3.1.1
    running build_docs
    Using source directory /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/TraitsGUI_3.1.1/docs/source
    Running Sphinx v0.6.2
    loading pickled environment... not found
    building [html]: targets for 0 source files that are out of date
    updating environment: 0 added, 0 changed, 0 removed
    WARNING: master file /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/TraitsGUI_3.1.1/docs/source/index.rst not found
    looking for now-outdated files... none found
    no targets are out of date.
    Running "/usr/bin/python setup.py develop --no-deps" within dir "/home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/TraitsBackendWX_3.2.1"
    running develop
    unrecognized .svn/entries format; skipping .
    running egg_info
    writing requirements to TraitsBackendWX.egg-info/requires.txt
    writing TraitsBackendWX.egg-info/PKG-INFO
    writing namespace_packages to TraitsBackendWX.egg-info/namespace_packages.txt
    writing top-level names to TraitsBackendWX.egg-info/top_level.txt
    writing dependency_links to TraitsBackendWX.egg-info/dependency_links.txt
    unrecognized .svn/entries format in
    reading manifest file 'TraitsBackendWX.egg-info/SOURCES.txt'
    writing manifest file 'TraitsBackendWX.egg-info/SOURCES.txt'
    running build_ext
    Creating /usr/local/lib/python2.6/dist-packages/TraitsBackendWX.egg-link (link to .)
    TraitsBackendWX 3.2.1.dev-r0 is already the active version in easy-install.pth

    Installed /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/TraitsBackendWX_3.2.1
    Running "/usr/bin/python setup.py develop --no-deps" within dir "/home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/EnvisagePlugins_3.1.2"
    running develop
    unrecognized .svn/entries format; skipping .
    running egg_info
    writing requirements to EnvisagePlugins.egg-info/requires.txt
    writing EnvisagePlugins.egg-info/PKG-INFO
    writing namespace_packages to EnvisagePlugins.egg-info/namespace_packages.txt
    writing top-level names to EnvisagePlugins.egg-info/top_level.txt
    writing dependency_links to EnvisagePlugins.egg-info/dependency_links.txt
    writing entry points to EnvisagePlugins.egg-info/entry_points.txt
    unrecognized .svn/entries format in
    reading manifest file 'EnvisagePlugins.egg-info/SOURCES.txt'
    writing manifest file 'EnvisagePlugins.egg-info/SOURCES.txt'
    running build_ext
    Creating /usr/local/lib/python2.6/dist-packages/EnvisagePlugins.egg-link (link to .)
    EnvisagePlugins 3.1.2.dev-r0 is already the active version in easy-install.pth

    Installed /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/EnvisagePlugins_3.1.2
    running build_docs
    Using source directory /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/EnvisagePlugins_3.1.2/docs/source
    Running Sphinx v0.6.2
    loading pickled environment... not found
    building [html]: targets for 0 source files that are out of date
    updating environment: 0 added, 0 changed, 0 removed
    WARNING: master file /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/EnvisagePlugins_3.1.2/docs/source/index.rst not found
    looking for now-outdated files... none found
    no targets are out of date.
    Running "/usr/bin/python setup.py develop --no-deps" within dir "/home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/Mayavi_3.3.1"
    running develop
    unrecognized .svn/entries format; skipping .
    running gen_docs
    Traceback (most recent call last):
      File "/usr/local/bin/ets", line 8, in <module>
        load_entry_point('ETSProjectTools==0.6.0.dev-r0', 'console_scripts', 'ets')()
      File "/usr/local/lib/python2.6/dist-packages/enthought/ets/ets.py", line 152, in main
        args.func(args, cfg)
      File "/usr/local/lib/python2.6/dist-packages/enthought/ets/develop.py", line 76, in main
        checkouts.perform(command, dry_run=args.dry_run)
      File "/usr/local/lib/python2.6/dist-packages/enthought/ets/tools/checkouts.py", line 126, in perform
        '%s' % project)
    RuntimeError: Unable to complete command for project: /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/Mayavi_3.3.1

[1]http://code.enthought.com/projects/mayavi/docs/development/html/mayavi/installation.html

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
MayaVi-users mailing list
MayaVi-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mayavi-users
Gael Varoquaux | 3 Jan 10:45 2010

Re: Installing mayavi bleeding edge

On Sun, Jan 03, 2010 at 10:41:35AM +0100, Michele Mattioni wrote:
>    I followed the instruction[1] to install the svn mayavi with all the
>    dependences, however I can install Mayavi properly.

> [snip]
>        running develop
>        unrecognized .svn/entries format; skipping .
>        running gen_docs
>        Traceback (most recent call last):
>          File "/usr/local/bin/ets", line 8, in <module>
>            load_entry_point('ETSProjectTools==0.6.0.dev-r0',
>    'console_scripts', 'ets')()
>          File
>    "/usr/local/lib/python2.6/dist-packages/enthought/ets/ets.py", line 152,
>    in main
>            args.func(args, cfg)
>          File
>    "/usr/local/lib/python2.6/dist-packages/enthought/ets/develop.py", line
>    76, in main
>            checkouts.perform(command, dry_run=args.dry_run)
>          File
>    "/usr/local/lib/python2.6/dist-packages/enthought/ets/tools/checkouts.py",
>    line 126, in perform
>            '%s' % project)
>        RuntimeError: Unable to complete command for project:
>    /home/mattions/Work/progs/Mayavi/Mayavi_3.3.1/Mayavi_3.3.1

I am not sure what the problem is (the error message seems confusing to
me), but it could be that you are victim of a bug in setuptools with
recent versions of SVN. What is your setuptools version number and what
is your SVN's version number?

Gaël

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
Michele Mattioni | 6 Jan 18:19 2010
Picon

Bug on cylinder length on visual module

Hi,

I opened this bug about the max length of a cylinder
https://svn.enthought.com/enthought/ticket/1859

Patch attached.

Is that the correct way?

Cheers,
Michele.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
MayaVi-users mailing list
MayaVi-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mayavi-users
Gael Varoquaux | 8 Jan 23:47 2010

Re: Bug on cylinder length on visual module

On Wed, Jan 06, 2010 at 05:19:07PM +0000, Michele Mattioni wrote:
>    Hi,

>    I opened this bug about the max length of a cylinder
>    [1]https://svn.enthought.com/enthought/ticket/1859

>    Patch attached.

>    Is that the correct way?

Hey,

Yes, that's pretty much the right way to do. Also, you should assing the
ticket to me, elsewhere, I'll never find out about it :).

The correct fix for the problem would be to use a trait that restricts to
positive numbers, rather than a range. I have committed your fix anyhow
(rev 25097).

Thanks a lot for the bug report and the fix. Sorry for being slow to
answer, I have a lot of things on my plate.

Gaël

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
Gael Varoquaux | 13 Jan 07:37 2010

Re: Code

On Fri, Dec 18, 2009 at 12:07:45PM -0700, Lang, Edward wrote:
>    I like the format of your program.  Is it possible for me to see the
>    python source code? I would like to use it to develop structural
>    engineering programs.

The source code is downloadable: 

http://www.enthought.com/repo/ETS/Mayavi-3.3.0.tar.gz

Gaël

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
Michele Mattioni | 17 Jan 13:39 2010
Picon

Re: Updated build of trunk-dev available



On Sun, Jan 17, 2010 at 9:44 AM, Fernando Perez <fperez.net <at> gmail.com> wrote:
On Sun, Jan 17, 2010 at 1:35 AM, Michele Mattioni <mattions <at> gmail.com> wrote:
> I tried to test the qt integration but it seems it doesn't work properly.
>
> The ipython doesn't release the prompt as it should (an as it happens with
> 0.10)
>
> I attach a rough script (and adaptation of Mayavi qt embedding), just for
> testing purpose.

Mmh, unfortunately I can't seem to run your script, because I get a traceback:

In [2]: run qt_embedding.py
Warning: Unable to import the qt4 backend for pyface due to traceback:
Traceback (most recent call last):
         File "/usr/lib/python2.6/dist-packages/enthought/pyface/toolkit.py",
line 40, in _init_toolkit
           __import__(be + 'init')
       ImportError: No module named qt4.init

Info: Unable to import any backend (qt4) for pyface; using the 'null'
toolkit instead.

/usr/lib/python2.6/dist-packages/enthought/traits/ui/toolkit.py:128:
UserWarning: Unable to import the 'qt4' backend for traits UI; using
the 'null' toolkit instead.
 "using the 'null' toolkit instead." % toolkit_name )
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)

/home/fperez/Desktop/qt_embedding.py in <module>()
    17     Int, Dict
    18 from enthought.traits.ui.api import View, Item
---> 19 from enthought.mayavi.core.ui.api import MayaviScene, MlabSceneModel, \
    20         SceneEditor
    21 from enthought.mayavi import mlab

ImportError: No module named api


This is on ubuntu karmic.  Do I need to run from SVN Enthought for this example?



Yes, the latest mayavi api for qt integration are only in the latest SVN Enthought

 
It would be great if we could have a smaller example illustrating your
problem that didn't depend on all of Enthought's machinery, because we
really want to make sure things work OK with Qt.  I've tried simpler
tests using matplotlib with qt, and those seem OK so far.
 

I tested with only qt and it works.

 
One thing to try:

1. Start ipython *without* --gui
2. At the ipython prompt, type
gui qt
3. Try to run your script.
 
Then, repeat, but with 'gui -a qt' instead.  Let us know if  it
produces any difference at all.


No difference.
 
If you have a simpler non-mayavi example, send it  our way.


It seems it's mayavi related, I'm adding the mayavi list to this mail.

Cheers,
Michele.
 
Thanks for the feedback!

_______________________________________________
IPython-dev mailing list
IPython-dev <at> scipy.org
http://mail.scipy.org/mailman/listinfo/ipython-dev
Fernando Perez | 18 Jan 01:09 2010
Picon

Re: Updated build of trunk-dev available

Hi Michele,

On Sun, Jan 17, 2010 at 4:39 AM, Michele Mattioni <mattions <at> gmail.com> wrote:
> Yes, the latest mayavi api for qt integration are only in the latest SVN
> Enthought

Ah, OK.  I don't have that right now, but eventually this will be very
high priority, it's just that first we need to get things right with
the stable releases of the various tools.

I did check with stable mayavi (wx) and pylab with wx backend, and
those two do coexist happily on the new branch.

>> It would be great if we could have a smaller example illustrating your
>> problem that didn't depend on all of Enthought's machinery, because we
>> really want to make sure things work OK with Qt.  I've tried simpler
>> tests using matplotlib with qt, and those seem OK so far.
>>
>
> I tested with only qt and it works.
>
>
>>
>> One thing to try:
>>
>> 1. Start ipython *without* --gui
>> 2. At the ipython prompt, type
>> gui qt
>> 3. Try to run your script.
>>
>>
>> Then, repeat, but with 'gui -a qt' instead.  Let us know if  it
>> produces any difference at all.
>>
>
> No difference.

OK, thanks for this feedback, we can track this further here:

https://bugs.launchpad.net/ipython/+bug/508953

Cheers,

f
Gael Varoquaux | 18 Jan 14:37 2010

Re: [MayaVi-users] Updated build of trunk-dev available

On Sun, Jan 17, 2010 at 12:39:22PM +0000, Michele Mattioni wrote:
>      Mmh, unfortunately I can't seem to run your script, because I get a
>      traceback:

>      In [2]: run qt_embedding.py
>      Warning: Unable to import the qt4 backend for pyface due to traceback:
>      Traceback (most recent call last):
>               File
>      "/usr/lib/python2.6/dist-packages/enthought/pyface/toolkit.py",
>      line 40, in _init_toolkit
>                 __import__(be + 'init')
>             ImportError: No module named qt4.init

>      Info: Unable to import any backend (qt4) for pyface; using the 'null'
>      toolkit instead.

>    Yes, the latest mayavi api for qt integration are only in the latest SVN
>    Enthought

I am a bit surprised. Fernando, could it be that you don't have the QT
backend installed for Traits? It will be named something like
'python-traitsbackendqt'.

Gaël
Fernando Perez | 18 Jan 23:54 2010
Picon

Re: [MayaVi-users] Updated build of trunk-dev available

Hey,

On Mon, Jan 18, 2010 at 5:37 AM, Gael Varoquaux
<gael.varoquaux <at> normalesup.org> wrote:
>
> I am a bit surprised. Fernando, could it be that you don't have the QT
> backend installed for Traits? It will be named something like
> 'python-traitsbackendqt'.
>

Thanks, that was it!  I didn't realize I hadn't installed enough of
the traits packages on my Karmic box, sorry...

Now I do get a different error though:

In [3]: run qt_embedding.py
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)

/home/fperez/Desktop/qt_embedding.py in <module>()
     17     Int, Dict
     18 from enthought.traits.ui.api import View, Item
---> 19 from enthought.mayavi.core.ui.api import MayaviScene, MlabSceneModel, \
     20         SceneEditor
     21 from enthought.mayavi import mlab

ImportError: No module named api

Is it possible to have a version of your script that runs with the
mayavi shipped in Karmic?

Because now with Gael's note and your script, I was able to test
things interactively:

In [1]: import os

In [2]: os.environ['ETS_TOOLKIT'] = 'qt4'

In [3]: gui qt

In [4]: from enthought.mayavi import mlab

In [5]: mlab.test_molecule ()
Out[5]:
(<enthought.mayavi.modules.glyph.Glyph object at 0xc949cbc>,
 <enthought.mayavi.modules.glyph.Glyph object at 0xd1002cc>,
 <enthought.mayavi.modules.glyph.Glyph object at 0xd13ecbc>,
 <enthought.mayavi.modules.glyph.Glyph object at 0xd152c8c>)

In [6]: mlab.figure()
Out[6]: <enthought.mayavi.core.scene.Scene object at 0xd2af65c>

In [7]: mlab.test_surf ()
Out[7]: <enthought.mayavi.modules.surface.Surface object at 0xdc381dc>

In [8]: mlab.test_surf ()
Out[8]: <enthought.mayavi.modules.surface.Surface object at 0xd16250c>

In [9]: pylab qt

Welcome to pylab, a matplotlib-based Python environment [backend: Qt4Agg].
For more information, type 'help(pylab)'.

In [10]: plt.figure()
Out[10]: <matplotlib.figure.Figure object at 0xdc5666c>

In [11]: plot(sin(linspace(0,2*pi,200)**2)
   ....: )
Out[11]: [<matplotlib.lines.Line2D object at 0xe69dbcc>]

In [12]:

And everything is fine: mayavi windows open up, their qt dialogs work,
I can then load pylab with the qt backend and it works, etc.  It's
*really* cool, in fact.

So I'd love to be able to reproduce your bug, so we can track it down
to either something we need to fix in ipython or something that can be
fixed upstream in mayavi...

Cheers,

f
Gael Varoquaux | 18 Jan 23:56 2010

Re: [IPython-dev] Updated build of trunk-dev available

On Mon, Jan 18, 2010 at 02:54:59PM -0800, Fernando Perez wrote:
> /home/fperez/Desktop/qt_embedding.py in <module>()
>      17     Int, Dict
>      18 from enthought.traits.ui.api import View, Item
> ---> 19 from enthought.mayavi.core.ui.api import MayaviScene, MlabSceneModel, \
>      20         SceneEditor
>      21 from enthought.mayavi import mlab

> ImportError: No module named api

Yes, that's new. You can just replace the api imports with the ones in:

https://svn.enthought.com/enthought/browser/Mayavi/trunk/enthought/mayavi/core/ui/api.py

HTH,

Gaël

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev

Gmane