Hi Jyri,
Jyri Virkki wrote:
> John Fischer wrote:
>> - Automatically find/download/install/upgrade dependencies at build
>> time using the EasyInstall tool, which supports downloading via
>> HTTP, FTP, Subversion, and SourceForge, and automatically scans web
>> pages linked from PyPI to find download links. (It's the closest
>> thing to CPAN currently available for Python.)
>
> Where do these bits end up by default? $HOME, `pwd`, somewhere else?
By default it will install in <python_home>/site-packages (in our case
/usr/lib/python2.4/site-packages. If you attempt to do this when you don't have
permissions, it returns with the error below which provides a lot of detail...
The default is not decided by easy_install, but is based on the Python distutils
configuration - this is part of Python itself.
You can use the "--install-dir" or "--prefix" options to re-direct to your own
private location, and if you do that you should modify the environment
PYTHONPATH to include this so that it's found automatically. I will try to
communicate this in the man-page when it's written.
There is another project (currently not slated for integration, but would be
easy to get using this one) called virtualenv which is very useful for creating
a virtual, private, install of python for many uses.
> Is there a "system" install where they become available to all users and/or
> a private install where they are available only by the user running this?
>
>> /usr/bin/eazy_install Uncommitted utility to install Egg Modules
>>
>> /usr/bin/eazy_install-2.4 Uncommitted Python version specific
>
> Is one a hard|soft link to the other? I assume the versioned one is
> to enable providing a newer one alongside in the future. If so don't
> you want the unversioned to be Volatile?
No they are not linked - they are separate copies.
I'm not sure about it being Volatile, the command path should still be
Uncommitted, no? The arguments and output are more likely to be Volatile.
Am I misinterpreting the purpose of listing the command-path interface as
Uncommitted?
>
> Do you anticipate a future /usr/bin/eazy_install-3.0 (or whichever) to
> also ship in SUNWpython-setuptools?
>
>
The version is based on the version of Python it refers and hence installs to.
Right now we have Python 2.4, I'm not sure why why 2.5 isn't there, but it's
not. So if python 2.5 was distributed, then we would have easy_install-2.5 also.
easy_install-2.4 might go away if python 2.4 goes away, I'm not sure how likely
it is that we would upgrade to 2.5 and remove 2.4 given the way we have multiple
version of Java now, but I guess that would be an ARC decision?
Hmm, given the above reasoning, maybe the versioned easy_install-<PythonVer> is
the one that is more likely to be Volatile, what do people think?
Thanks,
Darren.
---------------------------------- easy_install error output ------------------
error: can't create or remove files in install directory
The following error occurred while trying to add or remove files in the
installation directory:
[Errno 13] Permission denied:
'/usr/lib/python2.4/site-packages/test-easy-install-17162.write-test'
The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:
/usr/lib/python2.4/site-packages/
Perhaps your account does not have write access to this directory? If the
installation directory is a system-owned directory, you may need to sign in
as the administrator or "root" account. If you do not have administrative
access to this machine, you may wish to choose a different installation
directory, preferably one that is listed in your PYTHONPATH environment
variable.
For information on other options, you may wish to consult the
documentation at:
http://peak.telecommunity.com/EasyInstall.html
Please make the appropriate changes for your system and try again.
