As you can see, it's identical with the pip2.log. Could it be then, that there is even more programs that don't realize that their requirements have already being met?

As in, program not registering correctly for some reason, even when there is no visible errors during the installation? Ghost in the shell?

That happens sometimes, if you have some stuff installed via pip and some via apt-get and have both vanilla (non-debug) and debug versions of python. That's because of different versions of python requires related versions of packages.
Hmm, tried to check if I had any debug version of those, but didn't have those - just the normal ones. Could pytools conflict with setuptools? As installing pyopencl installs both pytools and numpy by default, it seems

At least when done through the software center.
Unlikelly, that's quite different packages, and currently I have both of them.
Now I see that the issue is here:
src/wrapper/wrap_cl.hpp:27:19: fatal error: CL/cl.h: No such file or directory
Might be wrong path to AMD_APP_SDK, check all related stuff.
https://bitcointalk.org/index.php?topic=57267.0http://wiki.tiker.net/OpenCLHowToBTW, any idea how to manually instruct the location of pyopencl to poclbm-skc? Or is the principle the same as in the instructions you referred to me?
Got it to work by separately installing the latest (2.9 at the time of writing) AMD APP SDK. Thank you for all that tried to help me