Successful build/install on Debian lenny amd64 against AMD/ATI beta4 drivers
by Neil Pilgrim
Hi everyone,
Just a note to say that I've now successfully managed to build pyopencl
on debian lenny amd64 (actually core2 duo) with the AMD/ATI drivers.
This machine has no suitable graphics card, so I'm using the AMD/ATI
drivers for the CPU part for testing.
I first downloaded both the driver and SDK archives, uncompressed them,
and copied the driver libraries from arch/x86_64/usr/lib64/ to the main
SDK lib directory, finally setting LD_LIBRARY_PATH to include that dir.
Building pyopencl was more tricky, and I eventually did something like:
- ensure I had the libboost*1.35.0 packages installed, rather than 1.34
(using package manager)
- (already had numpy)
- python configure.py ... with various options. I don't recall exactly,
but I ended up realising that siteconf.py held the options so if things
didn't work edited it by hand, leading to:
BOOST_INC_DIR = []
BOOST_LIB_DIR = []
BOOST_COMPILER = 'gcc42'
BOOST_PYTHON_LIBNAME = ['boost_python-gcc42-mt-1_35-py25']
BOOST_THREAD_LIBNAME = ['boost_thread-gcc42-mt-1_35']
CL_TRACE = False
CL_ENABLE_GL = False
SHIPPED_CL_HEADERS = False
CL_INC_DIR = ['SOMETHING/opencl/ati-stream-sdk-v2.0-beta4-lnx64/include/']
CL_LIB_DIR =
['SOMETHING/opencl/ati-stream-sdk-v2.0-beta4-lnx64/lib/x86_64/']
CL_LIBNAME = ['OpenCL']
CXXFLAGS = []
LDFLAGS = []
(note that I've put 'SOMETHING' where a more complex path really was,
but it should still be on one line not two)
- I tried 'make install', but wanted to install locally (home
directory), and some 'ctags' command failed, so in the end used:
python setup.py build
python setup.py install --home=$DIR (for some value of $DIR !)
where I'd made $DIR beforehand
- I set PYTHONPATH to $DIR/lib/python (I think!)
- CRITICALLY (?) I cd'ed away from the pyopencl directory (!) and then
"python -c 'import pyopencl'" worked without a problem :D
That was fun ;)
I'm hoping that a pyopencl package might appear in debian shortly...
Actual questions to follow shortly ;)
--
Neil
9 years, 10 months
compiling against multiple drivers
by Robert L Cloud
Hello gentlemen,
I'm trying to use opencl in my research and have been successfully able to compile pyopencl against the nvidia opencl library and the amd library but not both at the same time.
I would like to have access to the CPU and the GPU at once, and I'd imagine that this is a common desire. Is this possible? to use the NVIDIA GPU and the CPU in with opencl in the same pyopencl application(or any opencl application for that matter). how can I accomplish this?
thanks
9 years, 10 months
Re: [PyOpenCL] PyOpenCL Digest, Vol 2, Issue 12
by Steve Han
Hi,Andreas,
I have RMed setuptools-0.6c9-py2.6.egg in dirictory ~/site-packages and
/usr/bin/easy_install-2.6,but after "python -configure.py ..." the file
setuptools-0.6c9-py2.6.egg alway be generated in directory ~/pyopencl-0.91.3
and it remain reporting KeyError:'_cl' :
File
"/home/steve/Downloads/pyopencl-0.91.3/setuptools-0.6c9-py2.6.egg/setuptools/command/build_ext.py",
line 85, in get_ext_filename
KeyError: '_cl'
"This script requires setuptools version 0.6c9 to run (even to display
help). I will attempt to download it for you (from
http://pypi.python.org/packages/2.6/s/setuptools/), but
you may need to enable firewall access for this script first.
I will start the download in 15 seconds.
(Note: if this machine does not have network access, please obtain the file
http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c9-py2.6.egg
and place it in this directory before rerunning this script.)"
I use archlinux but I think that doesnt matter.
2009/10/20 <pyopencl-request(a)tiker.net>
> Send PyOpenCL mailing list submissions to
> pyopencl(a)tiker.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://tiker.net/mailman/listinfo/pyopencl_tiker.net
> or, via email, send a message with subject or body 'help' to
> pyopencl-request(a)tiker.net
>
> You can reach the person managing the list at
> pyopencl-owner(a)tiker.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of PyOpenCL digest..."
>
>
> Today's Topics:
>
> 1. Re: PyOpenCL Digest, Vol 2, Issue 9 (Andreas Kl?ckner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 19 Oct 2009 10:38:14 -0400
> From: Andreas Kl?ckner <lists(a)informa.tiker.net>
> Subject: Re: [PyOpenCL] PyOpenCL Digest, Vol 2, Issue 9
> To: pyopencl(a)tiker.net
> Message-ID: <200910191038.15860.lists(a)informa.tiker.net>
> Content-Type: text/plain; charset="iso-8859-15"
>
> On Sonntag 18 Oktober 2009, Steve Han wrote:
> > Thanks Andreas:
> > But how to get rid of setuptools from
> >
> "/usr/lib/python2.6/site-packages/setuptools-0.6c9-py2.6.egg/setuptools/__i
> > nit__.py".In my case,setuptools-0.6c9-py2.6.egg containing setuptools is
> a
> > file not a directory.
>
> Try
>
> apt-get remove --purge python-setuptools python-virtualenv
>
> if you installed it via the package manager, otherwise do
>
> rm -Rf /usr/lib/python2.6/site-packages/setuptools-0.6c9-py2.6.egg
> rm -Rf /usr/bin/easy_install
>
> Andreas
>
9 years, 11 months
Re: [PyOpenCL] PyOpenCL Digest, Vol 2, Issue 9
by Steve Han
Thanks Andreas:
But how to get rid of setuptools from
"/usr/lib/python2.6/site-packages/setuptools-0.6c9-py2.6.egg/setuptools/__init__.py".In
my case,setuptools-0.6c9-py2.6.egg containing setuptools is a file not a
directory.
2009/10/17 <pyopencl-request(a)tiker.net>
> Send PyOpenCL mailing list submissions to
> pyopencl(a)tiker.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://tiker.net/mailman/listinfo/pyopencl_tiker.net
> or, via email, send a message with subject or body 'help' to
> pyopencl-request(a)tiker.net
>
> You can reach the person managing the list at
> pyopencl-owner(a)tiker.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of PyOpenCL digest..."
>
>
> Today's Topics:
>
> 1. Re: Question about method invocation (Andreas Kl?ckner)
> 2. building error:KeyError:'_cl' (Steve Han)
> 3. Re: building error:KeyError:'_cl' (Andreas Kl?ckner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 15 Oct 2009 17:24:35 -0400
> From: Andreas Kl?ckner <lists(a)informa.tiker.net>
> Subject: Re: [PyOpenCL] Question about method invocation
> To: pyopencl(a)tiker.net
> Message-ID: <200910151724.37775.lists(a)informa.tiker.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Donnerstag 15 Oktober 2009, Nick Gaens wrote:
> > As you can see, the line which has "// ALERT" tailing shows five
> > parameters that are passed to the previously defined method which is
> > shown to only accept three.
> >
> > To make matters worse, I dugg into the reference op PyOpenCL and found
> > this: http://python-opencl.next-touch.com/tutorial.html#opencl-kernels.
> > This code is shown in the third colored box of this part of the
> reference:
> > [snip]
> > Can someone explain to me why these approaches are so inconsistent? Which
> > one is correct? What way is *the way to do it"?
>
> Well, there's an easy answer here. :)
>
> You're looking at the documentation for the wrong project. PyOpenCL's
> documentation is at [1] and, more specifically, [2]. In Tlapatlac's
> Python::OpenCL [3] and the other PyOpenCL [4] by Goncalo Carvalho are
> different projects.
>
> [1] http://documen.tician.de/pyopencl/
> [2]
> http://documen.tician.de/pyopencl/reference.html#pyopencl.Kernel.__call__
> [3] http://python-opencl.next-touch.com/
> [4] http://sourceforge.net/projects/pyopencl/
>
> Andreas
>
9 years, 11 months
Question about method invocation
by Nick Gaens
Hello all,
I'm a bit confused about a very small, although important part of PyOpenCL.
It concerns the way you invoke the written C-method from within Python.
While searching for some examples about this module, I found this:
http://git.tiker.net/pyopencl.git/blob/HEAD:/examples/benchmark-all.py
Running it shows that the OpenCL-part greatly improves the performance
of the calculations, but what isn't clear to me is the invocation of the
sum-method, which goes like this:
prg = cl.Program(ctx, """
__kernel void sum(__global const float *a, __global const
float *b, __global float *c) {
// do stuff
}
}
""").build()
exec_evt = prg.sum(queue, a.shape, a_buf, b_buf, dest_buf) // ALERT
exec_evt.wait()
As you can see, the line which has "// ALERT" tailing shows five
parameters that are passed to the previously defined method which is
shown to only accept three.
To make matters worse, I dugg into the reference op PyOpenCL and found
this: http://python-opencl.next-touch.com/tutorial.html#opencl-kernels.
This code is shown in the third colored box of this part of the reference:
__kernel void vector_add (__global char *c, __global char *a, __global char *b) {
// do stuff
}
prog = opencl.Program(opencl_source)
prog.vector_add(host_vec_out, host_vec_1, host_vec_2) // ALERT
Now, only three parameters are passed to the method, instead of five :-S.
Can someone explain to me why these approaches are so inconsistent? Which one is correct? What way is *the way to do it"?
Thx in advance,
Nick
9 years, 11 months
Indexing in 3D data
by Darcoux Christine
If I have *3D data of arbitrairy size*, how do I get the x, y and z
coordinates in the kernel?
Lets say I set up the 3D data like this
================================
import pyopencl as cl
import numpy
import numpy.linalg as la
a = numpy.random.rand((2,3,4)).astype(numpy.float32)
==========================================
And have a kernel something like this,
==============================================
prg = cl.Program(ctx, """
__kernel void polyn(__global const float *a, __global float *b)
{
int gid = get_global_id(0);
int x = ???????????????????????
int y = ???????????????????????
int z = ???????????????????????
b[gid] = a[gid] * x + 3 * y + 5 * z;
}
""").build()
prg.polyn(queue, a.shape, a_buf, dest_buf)
cl.enqueue_read_buffer(queue, dest_buf, a).wait()
print a
==============================================
1) How do upload the "a" array ?
2) How I get the x y and z coordinates for the current index in the volume?
I want to different things in the data depending on the x y and z
coordinates.
Thank you very much for your help
Christine
9 years, 11 months
building error:KeyError:'_cl'
by Steve Han
Hi list:
I am building pyopencl following the guide that linking
http://wiki.tiker.net/PyOpenCL/Installation/Linux and "make install" get the
error:KeyError:'_cl'.My "python configure.py" as the following:
--boost-inc-dir=/usr/include/boost-1_39 --boost-lib-dir=/usr/local/lib,/lib
--boost-python-libname=boost_python-gcc43-mt
--cl-inc-dir=/usr/lib/python2.6/site-packages/include
--cl-lib-dir=/usr/lib/python2.6/site-packages/lib --cl-libname=OpenCL
What wrong with me?How can I fix it?
Thanks a lof.
--
Best Regards,
Steve Han
9 years, 11 months
On Python 2.6.3 / distribute / setuptools
by Andreas Klöckner
Hi all,
--------------------------------------------------------------------------
This is relevant to you if you are using Python 2.6.3 and you are getting
errors of the sort:
"/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9-
py2.6.egg/setuptools/command/build_ext.py",
line 85, in get_ext_filename
KeyError: '_cl'
--------------------------------------------------------------------------
It seems Python 2.6.3 broke every C/C++ extension on the planet that was
shipped using setuptools (which includes PyCUDA, PyOpenCL, and many more of my
packages.) Thanks for your patience as I've worked through this mess, and to
both Allan and Christine, I'm sorry you've had to deal with this, and thanks
to Allan for pointing me in the right direction.
To make a long story short, I've switched my packages (including PyCUDA) to
use distribute instead of setuptools. All these changes are now in git. I'm
not sure this will help if a 2.6.3 user already has setuptools installed, but
I hope it will at least not make any other case worse. All in all, this seems
like the least bad option given that I expect distribute to be "the way of the
future".
Before I unleash this change full-scale, I would like it to get some testing.
For this purpose, I've created a PyCUDA release candidate package, here:
http://pypi.python.org/pypi/pycuda/0.93.1rc1
PLEASE TEST THIS, and speak up if you do--both positive and negative comments
are much appreciated.
Andreas
PS: Once I have reasonable confirmation that this works for PyCUDA, I'll also
release updated versions of PyOpenCL, meshpy, boostmpi, pyublas, .... The
relevant changes are *already in git* if you'd like to try them now.
PPS: Deciding in favor of distribute and against the promised setuptools
update was based on two factors:
- Primarily, distribute makes a fix for the 2.6.3 issue available *now*.
- Secondarily, I personally disliked the behavior of PJE, the author of
setuptools, in response to the current mess.
9 years, 11 months
Problems installing on Ubuntu 9.10 using NVIDIA
by Kristof Bamps
This is my configure line:
$ python configure.py --boost-inc-dir=/home/kristof/pool/include/boost/
--boost-lib-dir=$HOME/pool/lib
--boost-python-libname=boost_python-gcc44-mt
--cl-inc-dir=/home/kristof/NVIDIA_GPU_Computing_SDK/OpenCL/common/inc/
--cl-lib-dir=/home/kristof/NVIDIA_GPU_Computing_SDK/OpenCL/common/lib/
--cl-libname=OpenCL
when installing I get this error:
$ sudo make install
ctags -R src || true
/usr/bin/python setup.py install
running install
Checking .pth file support in /usr/local/lib/python2.6/dist-packages/
/usr/bin/python -E -c pass
TEST PASSED: /usr/local/lib/python2.6/dist-packages/ appears to support .pth
files
running bdist_egg
running egg_info
writing requirements to pyopencl.egg-info/requires.txt
writing pyopencl.egg-info/PKG-INFO
writing top-level names to pyopencl.egg-info/top_level.txt
writing dependency_links to pyopencl.egg-info/dependency_links.txt
reading manifest file 'pyopencl.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'src/cl/*.hpp'
writing manifest file 'pyopencl.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-i686/egg
running install_lib
running build_py
creating build
creating build/lib.linux-i686-2.6
creating build/lib.linux-i686-2.6/pyopencl
copying pyopencl/__init__.py -> build/lib.linux-i686-2.6/pyopencl
copying pyopencl/version.py -> build/lib.linux-i686-2.6/pyopencl
running build_ext
----------------------------------------------------------------------------
Sorry, your build failed. Try rerunning configure.py with different options.
----------------------------------------------------------------------------
Traceback (most recent call last):
File "setup.py", line 162, in <module>
main()
File "setup.py", line 154, in main
extra_link_args=conf["LDFLAGS"],
File "/home/kristof/School/Project
DB/Libs/pyopencl-0.91.3/aksetup_helper.py", line 12, in setup
setup(*args, **kwargs)
File "/usr/lib/python2.6/distutils/core.py", line 152, in setup
dist.run_commands()
File "/usr/lib/python2.6/distutils/dist.py", line 975, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.6/distutils/dist.py", line 995, in run_command
cmd_obj.run()
File
"/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9-py2.6.egg/setuptools/command/install.py",
line 76, in run
File
"/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9-py2.6.egg/setuptools/command/install.py",
line 96, in do_egg_install
File "/usr/lib/python2.6/distutils/cmd.py", line 333, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.6/distutils/dist.py", line 995, in run_command
cmd_obj.run()
File
"/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9-py2.6.egg/setuptools/command/bdist_egg.py",
line 174, in run
File
"/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9-py2.6.egg/setuptools/command/bdist_egg.py",
line 161, in call_command
File "/usr/lib/python2.6/distutils/cmd.py", line 333, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.6/distutils/dist.py", line 995, in run_command
cmd_obj.run()
File
"/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9-py2.6.egg/setuptools/command/install_lib.py",
line 20, in run
File "/usr/lib/python2.6/distutils/command/install_lib.py", line 113, in
build
self.run_command('build_ext')
File "/usr/lib/python2.6/distutils/cmd.py", line 333, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.6/distutils/dist.py", line 995, in run_command
cmd_obj.run()
File
"/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9-py2.6.egg/setuptools/command/build_ext.py",
line 46, in run
File "/usr/lib/python2.6/distutils/command/build_ext.py", line 340, in run
self.build_extensions()
File "/usr/lib/python2.6/distutils/command/build_ext.py", line 449, in
build_extensions
self.build_extension(ext)
File
"/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9-py2.6.egg/setuptools/command/build_ext.py",
line 175, in build_extension
File "/usr/lib/python2.6/distutils/command/build_ext.py", line 460, in
build_extension
ext_path = self.get_ext_fullpath(ext.name)
File "/usr/lib/python2.6/distutils/command/build_ext.py", line 635, in
get_ext_fullpath
filename = self.get_ext_filename(ext_name)
File
"/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9-py2.6.egg/setuptools/command/build_ext.py",
line 85, in get_ext_filename
KeyError: '_cl'
make: *** [install] Error 1
I'm guessing one or several of my configure options are faulty, but I'm
unsure which. I've tried changing them a bit for the past couple hours with
no effect.
9 years, 11 months
Problem installing on CentOS5 64-bit
by David Minor
Everything builds ok, but won't install.
here is my configure line:
./configure.py --boost-inc-dir=/space/local/include
--boost-lib-dir=/space/local/lib --boost-compiler=gcc41
--boost-python-libname=boost_python-gcc41-mt
--boost-thread-libname=boost_thread-gcc41-mt --update-user
Install gives me this error
[root@david-fc6 pyopencl_git]# make install
ctags -R src || true
/usr/bin/python setup.py install
running install
running bdist_egg
running egg_info
creating pyopencl.egg-info
writing requirements to pyopencl.egg-info/requires.txt
writing pyopencl.egg-info/PKG-INFO
writing top-level names to pyopencl.egg-info/top_level.txt
writing dependency_links to pyopencl.egg-info/dependency_links.txt
writing manifest file 'pyopencl.egg-info/SOURCES.txt'
reading manifest file 'pyopencl.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'src/cl/*.hpp'
writing manifest file 'pyopencl.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
running build_ext
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/pyopencl
copying build/lib.linux-x86_64-2.4/pyopencl/version.py ->
build/bdist.linux-x86_64/egg/pyopencl
copying build/lib.linux-x86_64-2.4/pyopencl/_cl.so ->
build/bdist.linux-x86_64/egg/pyopencl
copying build/lib.linux-x86_64-2.4/pyopencl/__init__.py ->
build/bdist.linux-x86_64/egg/pyopencl
byte-compiling build/bdist.linux-x86_64/egg/pyopencl/version.py to
version.pyc
byte-compiling build/bdist.linux-x86_64/egg/pyopencl/__init__.py to
__init__.pyc
creating stub loader for pyopencl/_cl.so
byte-compiling build/bdist.linux-x86_64/egg/pyopencl/_cl.py to _cl.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying pyopencl.egg-info/PKG-INFO ->
build/bdist.linux-x86_64/egg/EGG-INFO
copying pyopencl.egg-info/SOURCES.txt ->
build/bdist.linux-x86_64/egg/EGG-INFO
copying pyopencl.egg-info/dependency_links.txt ->
build/bdist.linux-x86_64/egg/EGG-INFO
copying pyopencl.egg-info/not-zip-safe ->
build/bdist.linux-x86_64/egg/EGG-INFO
copying pyopencl.egg-info/requires.txt ->
build/bdist.linux-x86_64/egg/EGG-INFO
copying pyopencl.egg-info/top_level.txt ->
build/bdist.linux-x86_64/egg/EGG-INFO
writing build/bdist.linux-x86_64/egg/EGG-INFO/native_libs.txt
creating dist
creating 'dist/pyopencl-0.91.3-py2.4-linux-x86_64.egg' and adding
'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing pyopencl-0.91.3-py2.4-linux-x86_64.egg
removing
'/usr/lib64/python2.4/site-packages/pyopencl-0.91.3-py2.4-linux-x86_64.e
gg' (and everything under it)
creating
/usr/lib64/python2.4/site-packages/pyopencl-0.91.3-py2.4-linux-x86_64.eg
g
Extracting pyopencl-0.91.3-py2.4-linux-x86_64.egg to
/usr/lib64/python2.4/site-packages
pyopencl 0.91.3 is already the active version in easy-install.pth
Installed
/usr/lib64/python2.4/site-packages/pyopencl-0.91.3-py2.4-linux-x86_64.eg
g
Processing dependencies for pyopencl==0.91.3
Searching for py>=1.0.2
Reading http://pypi.python.org/simple/py/
------------------------------------------------------------------------
----
Sorry, your build failed. Try rerunning configure.py with different
options.
------------------------------------------------------------------------
----
Traceback (most recent call last):
File "setup.py", line 162, in ?
main()
File "setup.py", line 154, in main
extra_link_args=conf["LDFLAGS"],
File "/export/space/downloads/pyopencl_git/aksetup_helper.py", line
12, in setup
setup(*args, **kwargs)
File "/usr/lib64/python2.4/distutils/core.py", line 149, in setup
dist.run_commands()
File "/usr/lib64/python2.4/distutils/dist.py", line 946, in
run_commands
self.run_command(cmd)
File "/usr/lib64/python2.4/distutils/dist.py", line 966, in
run_command
cmd_obj.run()
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/command/install.py", line 76, in run
self.do_egg_install()
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/command/install.py", line 104, in do_egg_install
cmd.run()
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/command/easy_install.py", line 211, in run
self.easy_install(spec, not self.no_deps)
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/command/easy_install.py", line 427, in easy_install
return self.install_item(None, spec, tmpdir, deps, True)
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/command/easy_install.py", line 478, in install_item
self.process_distribution(spec, dist, deps)
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/command/easy_install.py", line 518, in process_distribution
distros = WorkingSet([]).resolve(
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/pkg_resou
rces.py", line 522, in resolve
dist = best[req.key] = env.best_match(req, self, installer)
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/pkg_resou
rces.py", line 758, in best_match
return self.obtain(req, installer) # try and download/install
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/pkg_resou
rces.py", line 770, in obtain
return installer(requirement)
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/command/easy_install.py", line 432, in easy_install
dist = self.package_index.fetch_distribution(
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/package_index.py", line 462, in fetch_distribution
self.find_packages(requirement)
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/package_index.py", line 303, in find_packages
self.scan_url(self.index_url + requirement.unsafe_name+'/')
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/package_index.py", line 617, in scan_url
self.process_url(url, True)
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/package_index.py", line 189, in process_url
f = self.open_url(url, "Download error: %s -- Some packages may not
be found!")
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/package_index.py", line 579, in open_url
return open_with_auth(url)
File
"/usr/lib64/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/setuptool
s/package_index.py", line 717, in open_with_auth
fp = urllib2.urlopen(request)
File "/usr/lib64/python2.4/urllib2.py", line 130, in urlopen
return _opener.open(url, data)
File "/usr/lib64/python2.4/urllib2.py", line 358, in open
response = self._open(req, data)
File "/usr/lib64/python2.4/urllib2.py", line 376, in _open
'_open', req)
File "/usr/lib64/python2.4/urllib2.py", line 337, in _call_chain
result = func(*args)
File "/usr/lib64/python2.4/urllib2.py", line 573, in <lambda>
lambda r, proxy=url, type=type, meth=self.proxy_open: \
File "/usr/lib64/python2.4/urllib2.py", line 580, in proxy_open
if '@' in host:
TypeError: iterable argument required
make: *** [install] Error 1
9 years, 11 months
