Logged In: YES 
user_id=357491

I think modifying configure.in to detect the function is unnecessary; 
Darwin will be the only platform with it (Googling shows the CVS commit 
for Darwin that added the call to _CFInitialize() that probably set this 
whole problem off, so just blanket settting it (unless it is somehow new 
to OS X 10.3 or something) based on an ``#ifdef __APPLE__`` will 
probably be fine.  But knowing that function was explicitly added in a 
version would lead to requiring a configure.in check.

The next question becomes whether setting that value is a permanent 
settting in CoreFoundation until it is unloaded, or if it is just per run of an 
app.  If it is the former, then setting it period might be bad since that 
would affect other running apps.  But if Python is loaded against its own 
copy of CoreFoundation and it is local to Python then who cares; set the 
thing before any locale code is used and be done with it.

And as for accepting a patch, I know I would be happy with accepting it, 
but I would want Martin v. Lowis' input first to make sure this is the best 
thing to do.  Otherwise setlocale() should be changed to make it always 
raise an exception when __setonlyClocaleconv() is around.