Logged In: YES 
user_id=1216071

No, the problem does NOT exist with the dynamic library since 
it will reference versioned glibc-functions (i.e the dynamic 
python library will use the backward compatible functions that 
is present in glibc). 
 
This is why compiling and linking static library and application 
on the same system is not a problem; the resulting binary will 
run on both linuxthreads and NPTL systems, since they will use 
the versioned glibc functions. However, a static library does not 
reference versioned functions until it is linked with either a 
shared library or an application. Thus, if you compile the static 
library on a linuxthreads systems but link an application against 
it on a NPTL systems, things will break, since the static library 
expects an older version of glibc but gets linked against a new 
version. 
 
But yes, this is not a python bug. It jsut took some time for me 
fully understand the linking process regarding the versioned 
glibc functions.