Ronald Oussoren <ronaldousso...@mac.com> added the comment: Jack: could you please explain what the issue is? Unless you do so I will close this issue as "won't fix".
In particular: will linking with "-lpython3.0" work with this hypothetical future version of Xcode you're talking about? As mentioned before "libpythonX.Y.a" is present for compatibility with a number of popular 3th-party tools that have manually written makefiles that expect this library to be present. Making the file a symlink to the actual dylib in the framework seems to work as intented as the moment: the executable gets linked to the framework (just as if it was linked with "-framework Python") ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5514> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
