David> As a downstream distributor of Python, a major pain point for me
David> is when Python embeds a copy of a library's source code, rather
David> than linking against a system library (zlib, libffi and expat
David> spring to mind): if bugs (e.g. security issues) arise in a
David> library, I have to go chasing down all of the embedded copies of
David> the library, rather than having dynamic linking deal with it for
David> me.
The Unladen Swallow developers can correct me if I'm wrong, but I believe
the Subversion checkout holds a copy of LLVM strictly to speed development.
If the U-S folks find and fix a bug in LLVM they can shoot the fix upstream,
apply it locally, then keep moving forward without waiting for a new release
of LLVM. Support exists now for building with an external LLVM, and I would
expect that as Unladen Swallow moves out of active development into a more
stable phase of its existence that it will probably stop embedding LLVM.
Skip
_______________________________________________
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
