Jack: do I understand you correctly when I interpret your message to mean 
that libpython3.0.a inside the Python framework won't be usable as a 
library that's linked using '-lpython3.0' in a future edition of Xcode?

That would be a bummer. The current name was chosen because some 3th party 
code explicitly looks for a '.a' file (IIRC mod_python is one of those).

BTW. libpython3.0 is a symlink to the dylib in the Python.framework, 
specifically to allow applications that try to link to libpython to work.