Enthought builds: can i move my build to other machines (eg. in a tgz file?)

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Enthought builds: can i move my build to other machines (eg. in a tgz file?)

robert somerville
sorry  Peter:

Hey I'm quite confused by the online documentation (i'm a Python and Enthought newbie, and Confusion/Frustration index is VERY high)

I have successfully built ETS 3.4.1 , but i am confused , very uncertain on how to implement you responses previously... I would like to be able to move the build to other machines :: COULD you walk me through the process , in DETAIL (assume no minimal level of understanding) , of how to move my build to another machines ... my lack of experience with egg files, easy_install ,etc. is absolutely killing me ....

thanks for your foreboding/understanding;
Robert Somerville







_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Enthought builds: can i move my build to other machines (eg. in a tgz file?)

Lic. José M. Rodriguez Bacallao
I would like to see that too, also, with vtk, numpy, etc.

On 3/25/10, robert somerville <[hidden email]> wrote:

> sorry  Peter:
>
> Hey I'm quite confused by the online documentation (i'm a Python and
> Enthought newbie, and Confusion/Frustration index is VERY high)
>
> I have successfully built ETS 3.4.1 , but i am confused , very uncertain on
> how to implement you responses previously... I would like to be able to move
> the build to other machines :: COULD you walk me through the process , in
> DETAIL (assume no minimal level of understanding) , of how to move my build
> to another machines ... my lack of experience with egg files, easy_install
> ,etc. is absolutely killing me ....
>
> thanks for your foreboding/understanding;
> Robert Somerville
>


--
Lic. José M. Rodriguez Bacallao
Centro de Biofisica Medica
-----------------------------------------------------------------
Todos somos muy ignorantes, lo que ocurre es que no todos ignoramos lo mismo.

Recuerda: El arca de Noe fue construida por aficionados, el titanic
por profesionales
-----------------------------------------------------------------
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Enthought builds: can i move my build to other machines (eg. in a tgz file?)

Lic. José M. Rodriguez Bacallao
no one?

On 3/26/10, Lic. José M. Rodriguez Bacallao <[hidden email]> wrote:

> I would like to see that too, also, with vtk, numpy, etc.
>
> On 3/25/10, robert somerville <[hidden email]> wrote:
>> sorry  Peter:
>>
>> Hey I'm quite confused by the online documentation (i'm a Python and
>> Enthought newbie, and Confusion/Frustration index is VERY high)
>>
>> I have successfully built ETS 3.4.1 , but i am confused , very uncertain
>> on
>> how to implement you responses previously... I would like to be able to
>> move
>> the build to other machines :: COULD you walk me through the process , in
>> DETAIL (assume no minimal level of understanding) , of how to move my
>> build
>> to another machines ... my lack of experience with egg files,
>> easy_install
>> ,etc. is absolutely killing me ....
>>
>> thanks for your foreboding/understanding;
>> Robert Somerville
>>
>
>
> --
> Lic. José M. Rodriguez Bacallao
> Centro de Biofisica Medica
> -----------------------------------------------------------------
> Todos somos muy ignorantes, lo que ocurre es que no todos ignoramos lo
> mismo.
>
> Recuerda: El arca de Noe fue construida por aficionados, el titanic
> por profesionales
> -----------------------------------------------------------------
>


--
Lic. José M. Rodriguez Bacallao
Centro de Biofisica Medica
-----------------------------------------------------------------
Todos somos muy ignorantes, lo que ocurre es que no todos ignoramos lo mismo.

Recuerda: El arca de Noe fue construida por aficionados, el titanic
por profesionales
-----------------------------------------------------------------
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Enthought builds: can i move my build to other machines (eg. in a tgz file?)

Peter Wang
In reply to this post by robert somerville
On Thu, Mar 25, 2010 at 2:56 PM, robert somerville
<[hidden email]> wrote:
> I have successfully built ETS 3.4.1 , but i am confused , very uncertain on
> how to implement you responses previously... I would like to be able to move
> the build to other machines :: COULD you walk me through the process , in
> DETAIL (assume no minimal level of understanding) , of how to move my build
> to another machines ... my lack of experience with egg files, easy_install
> ,etc. is absolutely killing me ....

I'm going to assume that you know what Python packages and modules
are, and how they work.  If not, then please read this page:
http://docs.python.org/tutorial/modules.html

Given that knowledge, then the following definitions should make sense:

A Python egg is a zip file whose contents represent a Python package.
easy_install is the command you use to install egg files into your
system.  Before you can use the easy_install command, you need to
install either "setuptools" or "distribute".  distribute is the
preferred way.  Install by following the instructions here:
http://pypi.python.org/pypi/distribute#distribute-setup-py

Once you have the easy_install command, you can type "easy_install
<packagename> or "easy_install /path/to/egg/file".  The former command
will search the Python Package Index (PyPI, for short), for a matching
package, then download it, and then install it.  The latter command
just installs the local egg file into the Python site-packages
directory.

Note that you must have administrator-level rights for this to work.
On Unix systems you may need to do "sudo easy_install <packagename>".
It is also possible to do this without having administrator rights,
but that is just a little bit more complicated so I won't go into it
unless you really want to know.

Most python package do not have compiled C extensions, and are thus
cross-platform.  You can move the .egg files of those packages from a
Windows 64-bit system to a Linux 32-bit system, and as long as they
are running the same version of Python, and all of the packages that
the egg depends on exist on both platforms, then the egg will work.
However, packages like numpy, scipy, and certain packages in ETS do
have compiled C extensions, and thus cannot be easily moved across
machines of different architectures and platforms.

So, the short answer to your question about moving ETS packages to
different machines is this: if you build eggs on one machine, then you
can move those eggs to a different machine and run "easy_install" on
them, and they will work as long as those machines have the same
platform (architecture + OS + python version).  If they do not have
the same platform, then you cannot move your bulid across machines.

To build eggs from ETS, you just need to run "python setup.py
bdist_egg" inside each project's source directory.  This will produce
a .egg file inside the dist/ subdirectory.  To easily do this on all
projects, go to the directory with your ETS check out (not the
individual project subdirectories) and run "ets bdist".  This will
build all the projects' eggs into a subdirectory named dist/.

Hopefully this clears some things up.

-Peter
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev