headers
bryce hendrix | 1 Apr 01:29

Re: Reorganized install instructions on the Wiki

Minor technical points of note:

 * We support RHEL 4 as well as 3.
 * We require SWIG 1.3.31, I think
 * All of the new ets command line tools have been merged

Bryce

Gael Varoquaux wrote:
> I spent a good part of today rewritting and reorganizing the instruction
> for installing on the Wiki. The main page I came up with can be found on:
> https://svn.enthought.com/enthought/wiki/NewNewInstall
>
> My guideline for this reorganisation has been to try to avoid having
> information that gets outdated (no direct reference to release numbers).
>
> In addition I have tried limiting the repetition. The previous structure
> had an incredible amount of copy and pasted code, and as a result it was
> difficult to maintain, and actually some of the copy and pasted code was
> plain wrong (ie unixy commands on the windows-specific page).
>
> I would like some feedback from everybody on this rewrite. External
> people (ie non-developpers) are especially encouraged to give feedback.
>
> Once we all settle down on something we like, I'll replace the install
> page with this one, and update the instructions.
>
> Cheers,
>
> Gaël
(Continue reading)

Permalink | Reply | 3 comments |
headers
Gael Varoquaux | 1 Apr 01:29
Favicon
Gravatar

Re: Reorganized install instructions on the Wiki

On Mon, Mar 31, 2008 at 06:29:03PM -0500, bryce hendrix wrote:
> Minor technical points of note:

>  * We support RHEL 4 as well as 3.

I had a look at the download pages and I didn't seem to find the relevant
eggs.

>  * We require SWIG 1.3.31, I think

OK, thanks.

>  * All of the new ets command line tools have been merged

Could you please correct this part, as I am not too sure of how it should
be now (only the NewNewInstall page has to be corrected, this information
is not duplicated).

Cheers,

Gaël
Permalink | Reply | 2 comments |
headers
Dave Peterson | 1 Apr 01:46

Re: Reorganized install instructions on the Wiki

Gael Varoquaux wrote:
On Mon, Mar 31, 2008 at 06:29:03PM -0500, bryce hendrix wrote:
Minor technical points of note:
* We support RHEL 4 as well as 3.
I had a look at the download pages and I didn't seem to find the relevant eggs.

Because they have to be pulled from the RHEL 3 repo.  The previous instructions for that platform mentioned this. :-)  This is exactly why I think platform-specific and version specific instructions are the right way to go.

-- Dave

_______________________________________________
Enthought-dev mailing list
Enthought-dev@...
https://mail.enthought.com/mailman/listinfo/enthought-dev
Permalink | Reply | 1 comment |
headers
Gael Varoquaux | 1 Apr 01:50
Favicon
Gravatar

Re: Reorganized install instructions on the Wiki

On Mon, Mar 31, 2008 at 06:46:22PM -0500, Dave Peterson wrote:
>    Because they have to be pulled from the RHEL 3 repo.  The previous
>    instructions for that platform mentioned this. :-) 

Damn, I miss-read them.

>    This is exactly why I think platform-specific and version specific
>    instructions are the right way to go.

As you can see, I have tried keeping them, at least partly. I just
reduced the number of pages and tried to reduce duplication of
information (but I wasn't able to fully remove it).

I think it is important to underline that while going through the large
amount of platform-specific install information on the wiki, I did find
quite a few incorrectly copy and pasted information.

I'll update the pages using this information.

Cheers,

Gaël
Permalink | Reply | 0 comments |
headers
Dave Peterson | 1 Apr 01:59

Re: Reorganized install instructions on the Wiki

Gael Varoquaux wrote:
> I spent a good part of today rewritting and reorganizing the instruction
> for installing on the Wiki. The main page I came up with can be found on:
> https://svn.enthought.com/enthought/wiki/NewNewInstall
>
> My guideline for this reorganisation has been to try to avoid having
> information that gets outdated (no direct reference to release numbers).
>
> In addition I have tried limiting the repetition. The previous structure
> had an incredible amount of copy and pasted code, and as a result it was
> difficult to maintain, and actually some of the copy and pasted code was
> plain wrong (ie unixy commands on the windows-specific page).
>
> I would like some feedback from everybody on this rewrite. External
> people (ie non-developpers) are especially encouraged to give feedback.
>   

My thoughts:

 * The people who are least capable of doing command substitution are 
Windows users.  All example commands should therefore default to the 
version for Windows and you should ask other users to do the 
substitutions.  i.e. urls should be /enstaller/eggs/windows/xp instead 
of /enstaller/eggs/ubuntu/gutsy.

* The binary install example should install the full ETS, not just 
mayavi.  

* I personally don't like the fact that it is hard to see which Python 
versions are supported in your instructions.

I didn't even look at the build instructions because I've got to run home.

-- Dave
Permalink | Reply | 16 comments |
headers
Gael Varoquaux | 1 Apr 02:00
Favicon
Gravatar

Re: Reorganized install instructions on the Wiki

On Mon, Mar 31, 2008 at 06:59:02PM -0500, Dave Peterson wrote:
>  * The people who are least capable of doing command substitution are 
> Windows users.  All example commands should therefore default to the 
> version for Windows and you should ask other users to do the 
> substitutions.  i.e. urls should be /enstaller/eggs/windows/xp instead 
> of /enstaller/eggs/ubuntu/gutsy.

OK.

> * The binary install example should install the full ETS, not just 
> mayavi.  

OK.

> * I personally don't like the fact that it is hard to see which Python 
> versions are supported in your instructions.

Well, that's on purpose. I'd rather have that, than instructions not
updated as it is currently the case.

Gaël
Permalink | Reply | 15 comments |
headers
Dave Peterson | 1 Apr 14:20

Re: Enstaller Problems

rharder@... wrote:
> It seems that every enthought.* egg for windows has this bad line in  
> the dependency_links.txt file.  Could it just be deleted from the eggs  
> in the repository?
>
> This all worked just fine from the enstaller gui a month or two ago  
> and now it's failing.  Couldn't something be left in a reasonably  
> stable condition for the neophytes like me that just want to get up  
> and running?
>
>   

I hear your frustration and am sympathetic, but...

I have a hard time believing that the dependency link entries are the 
cause for any installation trouble (whether using enstaller or 
easy_install.)  It is more likely to be an issue with the fragility of 
enstaller (it breaks so often we no longer recommend using it in its 
currently released version), or problems with versioning and 
dependencies in older ETS releases.   Can you provide more information 
about what you are trying to do, how you did it so far, and what 
problems (i.e. output during installation) you saw?  Your original 
e-mail didn't include much information among those lines so it's hard to 
provide the right advice to you.

BTW: Those dependency link entries are the only way the installation 
works in many situations.  For example, for those installing on a 
platform for which we have no pre-built binaries, and also those using 
easy_install instead of enstaller.

-- Dave
Permalink | Reply | 0 comments |
headers
Prabhu Ramachandran | 1 Apr 15:58
Picon
Gravatar

Re: [MV2/T3] mayavi_traits_ui.py issue...

fred wrote:
> Hi,
> 
> I get a traceback using mayavi_traits_ui.py with Traits 3.0:
> 
[...]
>
"/usr/local/lib/python2.5/site-packages/TraitsGUI-3.0.0b1.dev_r18367-py2.5.egg/enthought/pyface/dock/dock_sizer.py", 
> line 211, in clear_window
>      dc.SetBrush( wx.Brush( wx.Colour( *BGColor ), wx.SOLID ) )
> TypeError: type object argument after * must be a sequence

I don't get this error at all from SVN.

> 
> I also get the message that gist_earth.gif is missing in core/lut,
> which is... true ;-)
> All gif files are missing.

Not true, see here:

https://svn.enthought.com/enthought/browser/Mayavi/trunk/enthought/mayavi/core/lut

files are there.

cheers,
prabhu
Permalink | Reply | 12 comments |
headers
Prabhu Ramachandran | 1 Apr 15:59
Picon
Gravatar

Re: [MV2] examples/streamline.py

fred wrote:
> I already posted the issue I get with this examples, under my etch box,
> using VTK from CVS and ETS built from source.
> 
> News are:
> 
> 1) I don't have this issue under Vista.
> 
> 2) I do get this issue under a ubuntu gutsy (live CD).
> Here's the snaphshot.
> 
> Nothing urgent, only informative.

Unfortunately, I have no idea about this one.  Possibly a graphics 
driver issue but not really sure.

cheers,
prabhu
Permalink | Reply | 1 comment |
headers
Prabhu Ramachandran | 1 Apr 16:02
Picon
Gravatar

Re: [MV2] displaying NaN...

fred wrote:
> BTW, do you have any idea about this ?
> 
> https://mail.enthought.com/pipermail/enthought-dev/2008-March/013232.html

I did respond to that with a suggestion to change your lut to make what 
you don't want to see transparent.  I also mailed you sample code to do 
this.  Doesn't that work?  The problem is with the way the image plane 
widget works.  I don't know of another solution apart from adjusting the 
lut as I described here:

https://mail.enthought.com/pipermail/enthought-dev/2008-March/013259.html

cheers,
prabhu
Permalink | Reply | 1 comment |

Gmane