Hi Omer,
> I'm seeing this on fc8 with a custom built python2.6. Not happening
> with any other packages (e.g. boto). Workaround of course was just to
> copy the S3 dir to /usr/local/lib/python2.6/site-packages.
I've found it. The culprit was a pre-set install prefix in setup.cfg - I
can't reme
Michal,
I'm seeing this on fc8 with a custom built python2.6. Not happening
with any other packages (e.g. boto). Workaround of course was just to
copy the S3 dir to /usr/local/lib/python2.6/site-packages.
I poked around a bit but nothing obvious jumped out. Happy to do any
debugging if you hav
Ping!
Does anyone know what the problem could be?
The bug reported provided some more information recently...
The modules have been installed to /usr/lib/python2.5/site-packages as
show below.
Apparently on his system /usr/lib/python2.5 is a symlink to
/System/Library/Frameworks/Python.framewor
Hi,
I have recently seen some reports from users of my s3cmd script [1] who
installed the package using the provided distutils-based setup.py and
immediately after installation the script failed to run because it
couldn't find its modules.
Here's an example session from Mac OS X, but similar beha
