Logged In: YES 
user_id=12800

BTW, this is a duplicate of 551353, which is currently
closed (and I'm keeping it closed since we don't need two
open bugs on the same issue).

However, in 551353 Martin outlines some approaches that a
user can take so that the .so files are properly found at
runtime.  I must disagree that Python can't do better.  We
hashed out a similar issue with the bsddb library which
installs in /usr/local/BerkeleyDB.X.Y by default, also not
on the default ld search path.  In that case we agreed to
add the setup.py magic to compile in the runtime path to the
library, and I think we should do the same with the ssl library.

setup.py already finds the dynamic libraries so it can just
as easily add the -R flag.  Too many people get bit by this
problem and there are basically no diagnostics to help
someone figure out what needs to be done to fix the problem.
 In 551353, Martin says that sometimes adding -R isn't
right, but I think for most people it will be right.  For
those that adding -R does the wrong thing, they can hack the
code, and I believe that adding -R will make life better for
the majority of users.

I assigned this to Guido for pronouncement.