Re: Attempting to build and install latest ETS>3.0.0b1 on Windows XP

Brennan Williams wrote:
> I'm trying to download, build and install all the latest bleeding edge 
> ETS, Traits 3, Chaco 3 etc under Windows XP.
>
> My initial problem is that I have failed to get "ets co" installed and 
> working.
>
> A bit of background, I'm downloading and building on my main notebook 
> which currently has ETS 3.0.0b1, Traits 3 and Chaco 3 from around February.
>
> I'm going to download into a g:\enthought directory structure, then 
> probably use egg_builder.py (mine is dated Jan 16th 2008 so I'll have a 
> look around the website first to see if I should be using something newer).
>
> Once I've built the eggs I'm going to do a clean install of Python 2.5 
> on another notebook, using the .msi from python.org. Then I'll install 
> the newly built eggs and then my app and then see what happens.
>
> Sound ok?
>
> So far, I have
>
> (1) looked at http://code.enthought.com/source/ and read about 
> ETSPackageTools
>
> (2) looked at https://svn.enthought.com/enthought/wiki/Build but decided 
> it wasn't what I wanted as I want to build ETS 3 on XP
>
> (3) gone to https://svn.enthought.com/enthought/wiki/SVNScripts, then 
> have done ...
>
>      
>
> svn co https://svn.enthought.com/svn/enthought/ETSProjectTools/trunk ETSProjectTools
> cd ETSProjectTools
> python setup.py install
>
>
> (4) checked that I have setuptools 0.6c7 or greater (I have 0.7a1dev_r53614)
>     I also have an enthought.setuptools.0.3.0a1_devr13502 dated Dec 19th 2007
>
> (5) done "ets co -h" which produced the following error....
>
>
> Traceback (most recent call last):
>   File "c:\python25\scripts\ets-script.py", line 8, in <module>
>     load_entry_point('ETSProjectTools==0.4.0a1.dev-r19423', 'console_scripts', 'ets')()
>   File
"C:\Python25\lib\site-packages\setuptools-0.7a1dev_r53614-py2.5.egg\pkg_resources.py",
line 236, in load_entry_point
>     return get_distribution(dist).load_entry_point(group, name)
>   File
"C:\Python25\lib\site-packages\setuptools-0.7a1dev_r53614-py2.5.egg\pkg_resources.py",
line 2015, in load_entry_point
>     return ep.load()
>   File
"C:\Python25\lib\site-packages\setuptools-0.7a1dev_r53614-py2.5.egg\pkg_resources.py",
line 1748, in load
>     entry = __import__(self.module_name, globals(),globals(), ['__name__'])
>   File
"c:\python25\lib\site-packages\ETSProjectTools-0.4.0a1.dev_r19423-py2.5.egg\enthought\ets\ets.py",
line 19, in <module>
>     from enthought.ets.build import Build
>   File
"c:\python25\lib\site-packages\ETSProjectTools-0.4.0a1.dev_r19423-py2.5.egg\enthought\ets\build.py",
line 13, in <module>
>     from enthought.ets.base_subcommand import BaseSubcommand
>   File
"c:\python25\lib\site-packages\ETSProjectTools-0.4.0a1.dev_r19423-py2.5.egg\enthought\ets\base_subcommand.py",
line 20, in <module>
>     from enthought.proxy.api import setup_proxy, setup_authentication
> ImportError: cannot import name setup_authentication
>
> (6) went back and clicked on "Troubleshooting", read the bit about setup_authentication and Enstaller,
edited my easy-install.pth
>     and removed the following two lines...
>
> ../enthought.enstaller.gui-2.2.0b4.dev_r16373-py2.5.egg
> ../enthought.enstaller-2.2.0b4.dev_r16404-py2.5.egg
>
> (7) tried "ets co -h" again but I still have the same error. How do I get my installation to recognise the
updated easy-install.pth?
>
>  (8) rebooted but still same problem
>
> (9) moved my enstaller egg and enthought.enstaller egg into an /obsolete directory but still same problem.
>
> Brennan
>
>
>   
an update to the above. I did a find . -name "proxy" -print in my 
site-packages directory (I like using Unix tools under Windows) and 
found another proxy in packagetools.

And taking another look at the http://code.enthought.com/source/ page I 
see it mentions both ETSPackageTools and ETSProjectTools

So I'm guessing that ETSPackageTools replaced PackageTools and then was 
renamed to ETSProjectTools. I'm sure I've glanced at some postings about 
this.

So I've moved my old PackageTools eggs to my obsolete directory and now 
it looks like "ets co" is going to work.

So perhaps the TroubleShooting info should be modified to mention the 
proxy in PackageTools?

Moving on...

Brennan