Ronald Oussoren ronaldousso...@mac.com added the comment:
I'm closing this issue because the user does not respond to my questions
and because I don't agree there is a problem.
--
resolution: - invalid
status: open - closed
___
Python tracker
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
Changes by Ronald Oussoren ronaldousso...@mac.com:
--
assignee: - ronaldoussoren
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5514
___
___
Ronald Oussoren ronaldousso...@mac.com added the comment:
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
New submission from Jack Howarth howa...@bromo.med.uc.edu:
The libpython3.0.a created for Python 3.0.1 isn't a normal static
library.
file
/System/Library/Frameworks/Python.framework/Versions/3.0/lib/python3.0/c
onfig/libpython3.0.a
